CVE-2026-68278

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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:

  • 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.
  • 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[].
  • 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.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Vendor Advisories for CVE-2026-68278(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-19 17:25 UTCGHSA enrichment
  2. 2026-08-19 17:21 UTCNVD update
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 16:54 UTCGHSA enrichment
  5. 2026-08-19 16:43 UTCMITRE cvelistV5
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 05:37 UTCGHSA enrichment
  8. 2026-08-17 05:26 UTCNVD update
  9. 2026-08-17 05:07 UTCGHSA enrichment
  10. 2026-08-17 05:05 UTCMITRE cvelistV5
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 03:44 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 08:35 UTCEG score recompute
  16. 2026-08-13 08:35 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-10 13:24 UTCNVD update
  19. 2026-08-10 12:19 UTCEG score recompute
  20. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68278?
CVE-2026-68278 is a publicly disclosed vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/dp/mst: fix buffer overflows in sideband chunk accumulation drmdpsidebandappendpayload() has three related bugs when processing device-provided sideband reply data: 1. Zero-length curchunklen underflow: msglen is a 6-bit field…
When was CVE-2026-68278 disclosed?
CVE-2026-68278 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68278 actively exploited?
CVE-2026-68278 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.5% of all scored CVEs.
How do I remediate CVE-2026-68278?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68278, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68278

Explore →

Is Your Infrastructure Affected by CVE-2026-68278?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.