public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Siddh Raman Pant <siddh.raman.pant@oracle.com>
Cc: "cve@kernel.org" <cve@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: CVE-2024-42308: drm/amd/display: Check for NULL pointer
Date: Wed, 9 Oct 2024 15:56:40 +0200	[thread overview]
Message-ID: <2024100917-launder-hamper-723b@gregkh> (raw)
In-Reply-To: <2fc2ba4addfbe40f7de3a5dfb146a3bdd3fc3edf.camel@oracle.com>

On Mon, Oct 07, 2024 at 11:01:59AM +0000, Siddh Raman Pant wrote:
> On Sat, 17 Aug 2024 11:10:13 +0200, Greg Kroah-Hartman wrote:
> > In the Linux kernel, the following vulnerability has been resolved:
> > 
> > drm/amd/display: Check for NULL pointer
> > 
> > [why & how]
> > Need to make sure plane_state is initialized
> > before accessing its members.
> > 
> > (cherry picked from commit 295d91cbc700651782a60572f83c24861607b648)
> > 
> > The Linux kernel CVE team has assigned CVE-2024-42308 to this issue.
> 
> This commit is no-op / doesn't make any difference, as there is an
> implicit NULL check rigth above it, as plane_state cannot be NULL
> (checked at the start of function).
> 
> So this CVE should be invalid.

Yeah, tricky code, I see why the static tools got this wrong.  I'll go
invalidate this now, thanks for the report!

greg k-h

      reply	other threads:[~2024-10-09 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024081751-CVE-2024-42308-562d@gregkh>
2024-10-07 11:01 ` CVE-2024-42308: drm/amd/display: Check for NULL pointer Siddh Raman Pant
2024-10-09 13:56   ` gregkh [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=2024100917-launder-hamper-723b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=siddh.raman.pant@oracle.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