The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Cengiz Can <cengiz.can@canonical.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
	linux-cve-announce@vger.kernel.org, security@ubuntu.com
Subject: Re: CVE-2021-47188: scsi: ufs: core: Improve SCSI abort handling
Date: Tue, 6 Aug 2024 08:41:34 +0200	[thread overview]
Message-ID: <2024080630-cinema-jukebox-8e5e@gregkh> (raw)
In-Reply-To: <otjby7on74mc3sx56xynqdnce2d2jmql57jvrgp6wvbo2knqbc@tm3udmcrp7gn>

On Mon, Aug 05, 2024 at 07:48:13PM +0300, Cengiz Can wrote:
> Hello,
> 
> I'm trying to figure out the security impact here:
> 
> > That warning is triggered by the following statement:
> > 
> > 	WARN_ON(lrbp->cmd);
> 
> This is just a fix to silence a warning. How is this worthy of a CVE? What was
> the criteria here?
> 
> If there are security implications of not nullifying `lrbp->cmd`, shouldn't they
> be noted in the CVE description?

CVE descriptions come directly from the kernel changelog text.  If you
wish them to say something else, please submit a patch against that text
and we can apply that.

> If this just a fix to the warning, this CVE should be rejected.

If userspace can trigger a WARN_ON() then the machine can be rebooted if
panic-on-warn is enabled, and so it requires a CVE assignment.

thanks

greg k-h

      reply	other threads:[~2024-08-06  6:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024041034-CVE-2021-47188-092a@gregkh>
2024-08-05 16:48 ` CVE-2021-47188: scsi: ufs: core: Improve SCSI abort handling Cengiz Can
2024-08-06  6:41   ` Greg Kroah-Hartman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024080630-cinema-jukebox-8e5e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cengiz.can@canonical.com \
    --cc=cve@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@ubuntu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox