CVE-2026-68278 — drm/dp/mst: fix buffer overflows in sideband chunk accumulation
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd and < ef2ecb6cf268debf3890df99fea01b6452dcf78e≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd and < d4e05dedb252ed3e540a0c9be511e427f098110a≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd and < 4d5109075a787de28c9e89940f9dee45269f91fa≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd and < 53937a2787d29c7a460e984dc4f20ff6ac91dc65≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd and < ef0dbcc200c3389f1f781ab181932a97e54b51af≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd and < 1e5827839ad0ceb0079d1560c321fa3656b54f21≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd and < a6366b551079c79bf7bdbadd74c97358bcfe2d58≥ ad7f8a1f9ced7f049f9b66d588723f243a7034cd and < 55bd5e685bda455b9b50c835f8c8442d52a344a3 and 1 moreversion 3.17 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.24%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/ef2ecb6cf268debf3890df99fea01b6452dcf78e
- git.kernel.org/stable/c/4d5109075a787de28c9e89940f9dee45269f91fa
- git.kernel.org/stable/c/55bd5e685bda455b9b50c835f8c8442d52a344a3
- git.kernel.org/stable/c/ef0dbcc200c3389f1f781ab181932a97e54b51af
- git.kernel.org/stable/c/53937a2787d29c7a460e984dc4f20ff6ac91dc65
- git.kernel.org/stable/c/1e5827839ad0ceb0079d1560c321fa3656b54f21
- git.kernel.org/stable/c/d4e05dedb252ed3e540a0c9be511e427f098110a
- git.kernel.org/stable/c/a6366b551079c79bf7bdbadd74c97358bcfe2d58
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68278 is "drm/dp/mst: fix buffer overflows in sideband chunk accumulation", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.