From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-53137: drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size
Date: Thu, 25 Jun 2026 09:39:45 +0100 [thread overview]
Message-ID: <2026062543-CVE-2026-53137-e711@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Clamp HDMI HDCP2 rx_id_list read to buffer size
[Why & How]
During HDCP 2.x repeater authentication over HDMI, the driver reads the
sink's RxStatus register and extracts a 10-bit message size field (max
value 1023). This value is used as the read length for the ReceiverID
list without being clamped to the size of the destination buffer
rx_id_list[177]. A malicious HDMI repeater could advertise a message
size larger than the buffer, causing an out-of-bounds write during the
I2C read.
Clamp the read length in mod_hdcp_read_rx_id_list() to the size of the
rx_id_list buffer, matching the approach already used in the DP branch.
(cherry picked from commit 229212219e4247d9486f8ba41ef087358490be09)
The Linux kernel CVE team has assigned CVE-2026-53137 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.6 with commit eff682f83c9c2030761e7536c5d97e1b20f71c15 and fixed in 5.10.259 with commit 3c4444aec06c74fbc05661f370954ac814963c38
Issue introduced in 5.6 with commit eff682f83c9c2030761e7536c5d97e1b20f71c15 and fixed in 5.15.210 with commit 91fb41218c413989d8b6c837748751454b452d68
Issue introduced in 5.6 with commit eff682f83c9c2030761e7536c5d97e1b20f71c15 and fixed in 6.1.176 with commit 964e50ef7b8f09815a7d05b8326af700f8d5bc96
Issue introduced in 5.6 with commit eff682f83c9c2030761e7536c5d97e1b20f71c15 and fixed in 6.6.143 with commit 79e0273272a05fb26f9b1e55bf1a52eefc3b7b35
Issue introduced in 5.6 with commit eff682f83c9c2030761e7536c5d97e1b20f71c15 and fixed in 6.12.94 with commit bfba882cfcd08f6540f72f48e786b6404f5d2c5b
Issue introduced in 5.6 with commit eff682f83c9c2030761e7536c5d97e1b20f71c15 and fixed in 6.18.36 with commit 1906064d50d194a145486e5caf3db3e708b6f6ef
Issue introduced in 5.6 with commit eff682f83c9c2030761e7536c5d97e1b20f71c15 and fixed in 7.0.13 with commit 98cfb7530ea91d8e5e928285cdce58e1131f6e83
Issue introduced in 5.6 with commit eff682f83c9c2030761e7536c5d97e1b20f71c15 and fixed in 7.1 with commit f0f3981c43b32cadfe373d636d9e9ca522bb3702
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-53137
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/modules/hdcp/hdcp_ddc.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/3c4444aec06c74fbc05661f370954ac814963c38
https://git.kernel.org/stable/c/91fb41218c413989d8b6c837748751454b452d68
https://git.kernel.org/stable/c/964e50ef7b8f09815a7d05b8326af700f8d5bc96
https://git.kernel.org/stable/c/79e0273272a05fb26f9b1e55bf1a52eefc3b7b35
https://git.kernel.org/stable/c/bfba882cfcd08f6540f72f48e786b6404f5d2c5b
https://git.kernel.org/stable/c/1906064d50d194a145486e5caf3db3e708b6f6ef
https://git.kernel.org/stable/c/98cfb7530ea91d8e5e928285cdce58e1131f6e83
https://git.kernel.org/stable/c/f0f3981c43b32cadfe373d636d9e9ca522bb3702
reply other threads:[~2026-06-25 8:43 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=2026062543-CVE-2026-53137-e711@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