From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-42308: drm/amd/display: Check for NULL pointer
Date: Sat, 17 Aug 2024 11:10:13 +0200 [thread overview]
Message-ID: <2024081751-CVE-2024-42308-562d@gregkh> (raw)
Description
===========
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.
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
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-42308
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/amd/display/dc/core/dc_surface.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f068494430d15b5fc551ac928de9dac7e5e27602
https://git.kernel.org/stable/c/4ccd37085976ea5d3c499b1e6d0b3f4deaf2cd5a
https://git.kernel.org/stable/c/185616085b12e651cdfd11ef00d1449f54552d89
https://git.kernel.org/stable/c/4ab68e168ae1695f7c04fae98930740aaf7c50fa
next reply other threads:[~2024-08-17 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 9:10 Greg Kroah-Hartman [this message]
2024-10-07 11:01 ` CVE-2024-42308: drm/amd/display: Check for NULL pointer Siddh Raman Pant
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=2024081751-CVE-2024-42308-562d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.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.