From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43320: drm/amd/display: Fix dsc eDP issue
Date: Fri, 8 May 2026 15:26:23 +0200 [thread overview]
Message-ID: <2026050819-CVE-2026-43320-061b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix dsc eDP issue
[why]
Need to add function hook check before use
The Linux kernel CVE team has assigned CVE-2026-43320 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.75 with commit 11718976c53a258c4d107aa05d68773379d0006f
Fixed in 6.18.16 with commit c10fe9471f3aa352bb9d9329d0b25e28e0672243
Fixed in 6.19.6 with commit 0481be9f12d8324789ccebf1e5fd0704b6e3fc99
Fixed in 7.0 with commit 878a4b73c11111ff5f820730f59a7f8c6fd59374
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-2026-43320
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/hwss/dce110/dce110_hwseq.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/11718976c53a258c4d107aa05d68773379d0006f
https://git.kernel.org/stable/c/c10fe9471f3aa352bb9d9329d0b25e28e0672243
https://git.kernel.org/stable/c/0481be9f12d8324789ccebf1e5fd0704b6e3fc99
https://git.kernel.org/stable/c/878a4b73c11111ff5f820730f59a7f8c6fd59374
reply other threads:[~2026-05-08 13:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2026050819-CVE-2026-43320-061b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox