CVE-2026-68445

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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/vc4: Prevent shader BO mappings from becoming writable

vc4_gem_object_mmap() rejects a writable mapping of a validated shader BO, but leaves VM_MAYWRITE set. Userspace can map the BO read-only and then turn it writable with mprotect().

Validated shader BOs must stay read-only: the validator checks the instructions once and the GPU trusts them afterwards. A writable mapping lets userspace rewrite the code after validation, bypassing the validator.

Clear VM_MAYWRITE on the read-only path so the mapping cannot be upgraded, as i915 already does for its read-only objects.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

drm/vc4: Prevent shader BO mappings from becoming writable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe168ef1d232d734d9998fd74822e2e20930dfff
generic

drm/vc4: Prevent shader BO mappings from becoming writable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f0ee411fc2d76333d6087c5862ffa907cf7a175
generic

drm/vc4: Prevent shader BO mappings from becoming writable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6deaa317201851c644c431b57682e54d06b35838
generic

drm/vc4: Prevent shader BO mappings from becoming writable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c9e6367639548307d3f578f6943ce72c9d39087
generic

drm/vc4: Prevent shader BO mappings from becoming writable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/019e6ad247f7fd038d2e009789f6d9bfcccb1ae7

Vendor Advisories for CVE-2026-68445(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 35× in last 7d / 45× 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-21 05:03 UTCEG score recompute
  2. 2026-08-21 05:03 UTCVendor advisory
  3. 2026-08-21 05:03 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 17:36 UTCGHSA enrichment
  6. 2026-08-20 06:06 UTCGHSA enrichment
  7. 2026-08-19 18:39 UTCEG score recompute
  8. 2026-08-19 18:39 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 05:40 UTCGHSA enrichment
  11. 2026-08-18 18:13 UTCEG score recompute
  12. 2026-08-18 18:13 UTCGHSA enrichment
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 06:45 UTCGHSA enrichment
  16. 2026-08-17 19:15 UTCEG score recompute
  17. 2026-08-17 19:15 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 06:31 UTCEG score recompute
  20. 2026-08-17 06:30 UTCGHSA enrichment
  21. 2026-08-17 05:35 UTCEG score recompute
  22. 2026-08-17 05:35 UTCGHSA enrichment
  23. 2026-08-16 20:28 UTCEG score recompute
  24. 2026-08-16 20:28 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 20 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 09:00 UTCEG score recompute
  3. 2026-08-16 09:00 UTCGHSA enrichment
  4. 2026-08-15 21:33 UTCGHSA enrichment
  5. 2026-08-15 10:06 UTCEG score recompute
  6. 2026-08-15 10:06 UTCGHSA enrichment
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 22:39 UTCGHSA enrichment
  9. 2026-08-14 11:12 UTCEG score recompute
  10. 2026-08-14 11:12 UTCGHSA enrichment
  11. 2026-08-13 23:45 UTCEG score recompute
  12. 2026-08-13 23:45 UTCGHSA enrichment
  13. 2026-08-13 23:03 UTCEG score recompute▲ 7.80
  14. 2026-08-13 23:03 UTCGHSA enrichment
  15. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-12 00:19 UTCNVD update
  19. 2026-08-12 00:15 UTCEG score recompute
  20. 2026-08-12 00:15 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-68445?
CVE-2026-68445 is a high vulnerability published on August 12, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/vc4: Prevent shader BO mappings from becoming writable vc4gemobject_mmap() rejects a writable mapping of a validated shader BO, but leaves VM_MAYWRITE set. Userspace can map the BO read-only and then turn it writable with…
When was CVE-2026-68445 disclosed?
CVE-2026-68445 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68445 actively exploited?
CVE-2026-68445 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-68445?
CVE-2026-68445 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68445?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68445, 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-68445

Explore →

Is Your Infrastructure Affected by CVE-2026-68445?

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

Start Free Scan →Browse All CVEs