CVE-2026-68240

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.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: 8.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/gpusvm: publish dpagemap early to avoid device mapping leak on error

drm_gpusvm_get_pages() only stored the local dpagemap into svm_pages->dpagemap on the success path. If a later page failed (e.g. -EOPNOTSUPP when ctx->allow_mixed is false) and jumped to err_unmap, svm_pages->dpagemap was still NULL, so __drm_gpusvm_unmap_pages() skipped device_unmap() and leaked the device mappings already created.

Assign svm_pages->dpagemap when the first device page is mapped so the err_unmap path can device_unmap() those mappings.

This issue was found by Sashiko AI review.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (3)

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

drm/gpusvm: publish dpagemap early to avoid device mapping leak on error - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/gpusvm: publish dpagemap early to avoid device mapping leak on error - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f708f51e3955bda0d77a0b67ab9bea6c97fea99
generic

drm/gpusvm: publish dpagemap early to avoid device mapping leak on error - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72e4fca5529e45b5beebad79d804de442f632324

Vendor Advisories for CVE-2026-68240(1)

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 38× in last 7d / 42× 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-20 15:17 UTCGHSA enrichment
  2. 2026-08-20 03:49 UTCEG score recompute
  3. 2026-08-20 03:49 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 16:19 UTCGHSA enrichment
  6. 2026-08-19 04:52 UTCGHSA enrichment
  7. 2026-08-18 17:25 UTCEG score recompute
  8. 2026-08-18 17:25 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 04:36 UTCGHSA enrichment
  12. 2026-08-17 17:06 UTCEG score recompute
  13. 2026-08-17 17:06 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 05:38 UTCEG score recompute
  16. 2026-08-17 05:38 UTCGHSA enrichment
  17. 2026-08-17 05:08 UTCEG score recompute
  18. 2026-08-17 05:08 UTCGHSA enrichment
  19. 2026-08-16 20:13 UTCEG score recompute
  20. 2026-08-16 20:13 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 08:45 UTCEG score recompute
  23. 2026-08-16 08:45 UTCGHSA enrichment
  24. 2026-08-15 21:18 UTCGHSA enrichment
  25. 2026-08-15 09:51 UTCEG score recompute
Show 17 more
  1. 2026-08-15 09:51 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 22:23 UTCGHSA enrichment
  4. 2026-08-14 10:56 UTCEG score recompute
  5. 2026-08-14 10:56 UTCGHSA enrichment
  6. 2026-08-13 23:29 UTCEG score recompute
  7. 2026-08-13 23:29 UTCGHSA enrichment
  8. 2026-08-13 22:44 UTCEG score recompute 8.80
  9. 2026-08-13 22:44 UTCGHSA enrichment
  10. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-13 19:20 UTCEG score recompute
  13. 2026-08-13 19:20 UTCGHSA enrichment
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-10 13:24 UTCNVD update
  16. 2026-08-10 12:19 UTCEG score recompute
  17. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68240?
CVE-2026-68240 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/gpusvm: publish dpagemap early to avoid device mapping leak on error drmgpusvmget_pages() only stored the local dpagemap into svm_pages->dpagemap on the success path. If a later page failed (e.g. -EOPNOTSUPP when…
When was CVE-2026-68240 disclosed?
CVE-2026-68240 was first published in the National Vulnerability Database on August 10, 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-68240 actively exploited?
CVE-2026-68240 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 94.2% of all scored CVEs.
What is the CVSS score of CVE-2026-68240?
CVE-2026-68240 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-68240?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68240, 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-68240

Explore →

Is Your Infrastructure Affected by CVE-2026-68240?

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