All of lore.kernel.org
 help / color / mirror / Atom feed
From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
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: Mon, 7 Oct 2024 11:01:59 +0000	[thread overview]
Message-ID: <2fc2ba4addfbe40f7de3a5dfb146a3bdd3fc3edf.camel@oracle.com> (raw)
In-Reply-To: <2024081751-CVE-2024-42308-562d@gregkh>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

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.

> Affected and fixed versions
> ===========================
> 
> 	Fixed in 6.1.103 with commit f068494430d1
> 	Fixed in 6.6.44 with commit 4ccd37085976
> 	Fixed in 6.10.3 with commit 185616085b12
> 	Fixed in 6.11-rc1 with commit 4ab68e168ae1

This also got backported to older kernels.

Thanks,
Siddh

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-10-07 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17  9:10 CVE-2024-42308: drm/amd/display: Check for NULL pointer Greg Kroah-Hartman
2024-10-07 11:01 ` Siddh Raman Pant [this message]
2024-10-09 13:56   ` gregkh

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=2fc2ba4addfbe40f7de3a5dfb146a3bdd3fc3edf.camel@oracle.com \
    --to=siddh.raman.pant@oracle.com \
    --cc=cve@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.