CVE-2026-68278

drm/dp/mst: fix buffer overflows in sideband chunk accumulation

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 buffer overflows in sideband chunk accumulation drm_dp_sideband_append_payload() has three related bugs when processing device-provided sideband reply data: 1. Zero-length curchunk_len underflow: msg_len is a 6-bit field taken directly from the DP sideband header. If a device sends msg_len=0, curchunk_len is set to zero. The condition (curchunk_idx >= curchunk_len) is immediately true, and curchunk_len-1 wraps to 255 (u8 underflow). drm_dp_msg_data_crc4() reads 255 bytes from chunk[48], then memcpy() writes 255 bytes into msg[], both far out of bounds. 2. chunk[48] overflow: curchunk_len can reach 63 (6-bit field). chunk[] is only 48 bytes. Multi-iteration payload assembly appends 16-byte blocks until curchunk_idx reaches curchunk_len, writing up to 15 bytes past the end of chunk[] into msg[]. 3. msg[256] overflow: each chunk contributes (curchunk_len-1) bytes to msg[]. No check ensures curlen + (curchunk_len-1) stays within msg[256], so the memcpy can spill into adjacent struct fields. All three are reachable from any DP MST device that can forge sideband reply messages on a physical connection.

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 1e5827839ad0ceb0079d1560c321fa3656b54f21 (fixed)
Vendor states this is fixed in 4d5109075a787de28c9e89940f9dee45269f91fa (fixed)
Vendor states this is fixed in 53937a2787d29c7a460e984dc4f20ff6ac91dc65 (fixed)
Vendor states this is fixed in 55bd5e685bda455b9b50c835f8c8442d52a344a3 (fixed)
Vendor states this is fixed in a6366b551079c79bf7bdbadd74c97358bcfe2d58 (fixed)
Vendor states this is fixed in d4e05dedb252ed3e540a0c9be511e427f098110a (fixed)
Vendor states this is fixed in ef0dbcc200c3389f1f781ab181932a97e54b51af (fixed)
Vendor states this is fixed in ef2ecb6cf268debf3890df99fea01b6452dcf78e (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