CVE-2026-68260

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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/imagination: acquire vm_ctx->lock before mapping memory to GPU VM

The drm gpuvm code doesn't protect find operation against map operation, and the driver needs to ensure a map operation shouldn't happen when a find operation is in progress.

In some cases a find operation will be in progress when doing map/unmap operations, and the find operation will do a NULL pointer dereference.

An example of the stack trace of such NULL dereference is shown below:

Unable to handle kernel access to user memory without uaccess routines at
virtual address 0000000000000010

[] drm_gpuva_find+0x28/0x6c [drm_gpuvm] [] pvr_vm_unmap+0x34/0x68 [powervr] [] pvr_ioctl_vm_unmap+0x2e/0x50 [powervr] [] drm_ioctl_kernel+0x8e/0xdc [] drm_ioctl+0x1be/0x3e0 [] __riscv_sys_ioctl+0xba/0xc4 [] do_trap_ecall_u+0x23e/0x3f4 [] handle_exception+0x168/0x174

As all occurences of drm_gpuva_find*() are already guarded by vm_ctx->lock, make pvr_vm_map() to acquire this lock to prevent disturbing any find operation. This fixes the NULL deference problem in drm_gpuva_find*().

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
6%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

drm/imagination: acquire vm_ctx->lock before mapping memory to GPU VM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6253bb56bb2ebdf317d8b599ce737a2510cc2e17
generic

drm/imagination: acquire vm_ctx->lock before mapping memory to GPU VM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f1f2618e44b21a7d4eb30d3bbd7e015ffbbbadf
generic

drm/imagination: acquire vm_ctx->lock before mapping memory to GPU VM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17e2030f37600994440f875dc410615d5c66ee6d
generic

drm/imagination: acquire vm_ctx->lock before mapping memory to GPU VM - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15f58d44c24477a6ebffa44ec05207b81cfa55d9

Vendor Advisories for CVE-2026-68260(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 33× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:31 UTCGHSA enrichment
  3. 2026-08-20 11:30 UTCGHSA enrichment
  4. 2026-08-20 00:28 UTCEG score recompute
  5. 2026-08-20 00:28 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 13:25 UTCGHSA enrichment
  8. 2026-08-19 02:20 UTCGHSA enrichment
  9. 2026-08-18 15:18 UTCEG score recompute
  10. 2026-08-18 15:18 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 03:41 UTCGHSA enrichment
  14. 2026-08-17 16:39 UTCEG score recompute
  15. 2026-08-17 16:39 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:37 UTCEG score recompute
  18. 2026-08-17 05:37 UTCGHSA enrichment
  19. 2026-08-17 05:07 UTCEG score recompute
  20. 2026-08-17 05:07 UTCGHSA enrichment
  21. 2026-08-17 04:58 UTCGHSA enrichment
  22. 2026-08-16 17:56 UTCEG score recompute
  23. 2026-08-16 17:56 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 06:54 UTCEG score recompute
Show 20 more
  1. 2026-08-16 06:54 UTCGHSA enrichment
  2. 2026-08-15 19:53 UTCGHSA enrichment
  3. 2026-08-15 08:51 UTCEG score recompute
  4. 2026-08-15 08:51 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 21:49 UTCGHSA enrichment
  7. 2026-08-14 10:47 UTCEG score recompute
  8. 2026-08-14 10:47 UTCGHSA enrichment
  9. 2026-08-13 23:46 UTCEG score recompute
  10. 2026-08-13 23:46 UTCGHSA enrichment
  11. 2026-08-13 22:44 UTCEG score recompute 7.80
  12. 2026-08-13 22:44 UTCGHSA enrichment
  13. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 19:37 UTCEG score recompute
  16. 2026-08-13 19:37 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(5)

What is CVE-2026-68260?
CVE-2026-68260 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/imagination: acquire vm_ctx->lock before mapping memory to GPU VM The drm gpuvm code doesn't protect find operation against map operation, and the driver needs to ensure a map operation shouldn't happen when a find operation is…
When was CVE-2026-68260 disclosed?
CVE-2026-68260 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-68260 actively exploited?
CVE-2026-68260 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68260?
CVE-2026-68260 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68260?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68260, 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-68260

Explore →

Is Your Infrastructure Affected by CVE-2026-68260?

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