CVE-2026-68279

drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers

N/A
Published: August 10, 2026 at 12:02 PM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers drm_dp_sideband_parse_remote_dpcd_read() reads num_bytes from the raw message and then unconditionally does: memcpy(bytes, &raw->msg[idx], num_bytes); without checking that idx + num_bytes <= raw->curlen. raw->msg[] is 256 bytes; if a malicious or misbehaving MST hub sets num_bytes larger than the remaining payload, the memcpy reads past the received data into whatever follows in raw->msg[]. drm_dp_sideband_parse_remote_i2c_read_ack() has the same flaw (noted with a /* TODO check */ comment since the code was introduced). Fix both functions by using a single combined check (idx + num_bytes > curlen) before each memcpy. Since num_bytes is u8, it is always >= 0, so this strictly subsumes the simpler idx > curlen form and no separate step is needed. [added missing fixes tag]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.17 ≤ v < 5.10.2663.17 ≤ v < 5.15.2173.17 ≤ v < 6.1.1833.17 ≤ v < 6.12.1013.17 ≤ v < 6.18.423.17 ≤ v < 6.6.1483.17 ≤ v < 7.1.63.17 ≤ v < 7.23.17ad7f8a1f9ced7f049f9b66d588723f243a7034cd
Vendor states this is fixed in 04d953f50d61e542e94a5977822cc53735f8c0ce (fixed)
Vendor states this is fixed in 185de1d74e658e2edb723ba76fa61903f77d8a68 (fixed)
Vendor states this is fixed in 1a8f537f5a1eeac941f262fe73078d6b08ba83c0 (fixed)
Vendor states this is fixed in 22d9f7fc1aaabaf73d5f30e8b0c9aa814ecd6ed2 (fixed)
Vendor states this is fixed in 533d9e2bede4aeefdc2a0561d7071cfede95958f (fixed)
Vendor states this is fixed in c2fbda0fe0163c55ba3820ee6cea0c6b43622eda (fixed)
Vendor states this is fixed in d7b9b1e33b4ed8c48d4db6e6e21c257ebbbb2586 (fixed)
Vendor states this is fixed in e6ef5455b06cb4e5d181aabcd723791587c79f12 (fixed)
Vendor states this is fixed in 3.17 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card