CVE-2026-68277

drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers

N/A
Published: August 10, 2026 at 12:01 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 on 2-byte fields in sideband reply parsers Three sideband reply parsers read 16-bit fields as: val = (raw->msg[idx] << 8) | (raw->msg[idx+1]); and check bounds only after the fact. When idx == raw->curlen, raw->msg[idx+1] reads one byte past the received message data into the following struct fields (curchunk_len, curchunk_idx, curlen). Affected functions: - drm_dp_sideband_parse_enum_path_resources_ack() full_payload_bw_number and avail_payload_bw_number fields - drm_dp_sideband_parse_allocate_payload_ack() allocated_pbn field - drm_dp_sideband_parse_query_payload_ack() allocated_pbn field Fix by using a single combined check (idx + 2 > curlen) before each 2-byte read. Since the check is strictly tighter than idx > curlen, no separate step is needed. [added 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 0bcd7675c69a2462a8531fcd9e4d096e9c7ec5df (fixed)
Vendor states this is fixed in 192e146c2d57ad033b0d418ec64ee390f8dc074e (fixed)
Vendor states this is fixed in 68a624416d1dd481b3e5b7ea0e8a070a9b8a2c73 (fixed)
Vendor states this is fixed in 6b89ba3dba2f583626fb693e47e951ffb8bf591f (fixed)
Vendor states this is fixed in 6e3107e6522109a07fc9bb0fc4ec463f1982e113 (fixed)
Vendor states this is fixed in bdf0508b1e6785d4a8982c637e97e68d60b47d7b (fixed)
Vendor states this is fixed in c1f72a13d54ffd16647d3fa540d961f5deba8790 (fixed)
Vendor states this is fixed in d5c70523cafa26ad2c7a37b612849abe2683baa8 (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