CVE-2026-46311

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu/userq: fix access to stale wptr mapping

Use drm_exec to take both locks i.e vm root bo and wptr_obj bo to access the mapping data properly.

This fixes the security issue of unmap the wptr_obj while a queue creation is in progress and passing other bo at same address.

(cherry picked from commit 1fc6c8ab45dbee096469c08c13f6099d57a52d6c)

CVSS v3
7.8
EG Score
7.8(medium)
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
2%
KEV
Not listed

Published

June 8, 2026

Last Modified

August 5, 2026

Advisory Details (2)

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

drm/amdgpu/userq: fix access to stale wptr mapping - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/userq: fix access to stale wptr mapping - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/336a9186f3a4b65bbd865d93936605ac8a1a3991

Vendor Advisories for CVE-2026-46311(1)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.9-1—

All Vendor Advisories

(9)

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 9× in last 7d / 47× 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.

Showing the most recent 100 of 253 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 04:49 UTCEG score recompute
  3. 2026-09-14 04:49 UTCVendor advisory
  4. 2026-09-14 04:49 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-08-31 01:51 UTCEG score recompute
  16. 2026-08-31 01:51 UTCVendor advisory
  17. 2026-08-31 01:51 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-25 01:21 UTCEG score recompute
  25. 2026-08-25 01:21 UTCVendor advisory
Show 75 more
  1. 2026-08-25 01:21 UTCGHSA enrichment
  2. 2026-08-24 01:11 UTCVendor advisory
  3. 2026-08-24 01:11 UTCGHSA enrichment
  4. 2026-08-23 11:45 UTCEG score recompute
  5. 2026-08-23 11:45 UTCVendor advisory
  6. 2026-08-23 11:45 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 01:39 UTCEG score recompute
  9. 2026-08-22 01:39 UTCVendor advisory
  10. 2026-08-22 01:39 UTCGHSA enrichment
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 12:29 UTCEG score recompute
  13. 2026-08-21 12:29 UTCVendor advisory
  14. 2026-08-21 12:29 UTCGHSA enrichment
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 22:39 UTCVendor advisory
  17. 2026-08-20 22:39 UTCGHSA enrichment
  18. 2026-08-20 09:28 UTCEG score recompute
  19. 2026-08-20 09:28 UTCVendor advisory
  20. 2026-08-20 09:28 UTCGHSA enrichment
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 06:40 UTCVendor advisory
  24. 2026-08-17 06:39 UTCGHSA enrichment
  25. 2026-08-16 16:20 UTCEG score recompute
  26. 2026-08-16 16:20 UTCVendor advisory
  27. 2026-08-16 16:20 UTCGHSA enrichment
  28. 2026-08-16 14:56 UTCEPSS rescore
  29. 2026-08-16 03:07 UTCEG score recompute
  30. 2026-08-16 03:07 UTCVendor advisory
  31. 2026-08-16 03:07 UTCGHSA enrichment
  32. 2026-08-16 02:14 UTCEPSS rescore
  33. 2026-08-15 13:57 UTCEG score recompute
  34. 2026-08-15 13:57 UTCVendor advisory
  35. 2026-08-15 13:57 UTCGHSA enrichment
  36. 2026-08-15 01:30 UTCEPSS rescore
  37. 2026-08-15 00:47 UTCVendor advisory
  38. 2026-08-15 00:47 UTCGHSA enrichment
  39. 2026-08-14 11:37 UTCVendor advisory
  40. 2026-08-14 11:37 UTCGHSA enrichment
  41. 2026-08-13 22:27 UTCEG score recompute
  42. 2026-08-13 22:27 UTCVendor advisory
  43. 2026-08-13 22:27 UTCGHSA enrichment
  44. 2026-08-13 22:00 UTCEPSS rescore
  45. 2026-08-13 06:31 UTCVendor advisory
  46. 2026-08-13 06:31 UTCGHSA enrichment
  47. 2026-08-12 17:21 UTCEG score recompute
  48. 2026-08-12 17:21 UTCVendor advisory
  49. 2026-08-12 17:21 UTCGHSA enrichment
  50. 2026-08-12 13:51 UTCEPSS rescore
  51. 2026-08-12 04:11 UTCVendor advisory
  52. 2026-08-12 04:11 UTCGHSA enrichment
  53. 2026-08-11 15:00 UTCEG score recompute
  54. 2026-08-11 15:00 UTCVendor advisory
  55. 2026-08-11 15:00 UTCGHSA enrichment
  56. 2026-08-11 01:49 UTCEG score recompute
  57. 2026-08-11 01:49 UTCVendor advisory
  58. 2026-08-11 01:49 UTCGHSA enrichment
  59. 2026-08-11 00:00 UTCEPSS rescore
  60. 2026-08-10 12:39 UTCVendor advisory
  61. 2026-08-10 12:39 UTCGHSA enrichment
  62. 2026-08-09 23:29 UTCEG score recompute
  63. 2026-08-09 23:29 UTCVendor advisory
  64. 2026-08-09 23:29 UTCGHSA enrichment
  65. 2026-08-09 13:46 UTCEPSS rescore
  66. 2026-08-09 10:19 UTCVendor advisory
  67. 2026-08-09 10:19 UTCGHSA enrichment
  68. 2026-08-08 21:07 UTCEG score recompute
  69. 2026-08-08 21:07 UTCVendor advisory
  70. 2026-08-08 21:07 UTCGHSA enrichment
  71. 2026-08-08 16:37 UTCEPSS rescore
  72. 2026-08-08 07:54 UTCVendor advisory
  73. 2026-08-08 07:54 UTCGHSA enrichment
  74. 2026-08-07 18:44 UTCEG score recompute
  75. 2026-08-07 18:44 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-46311?
CVE-2026-46311 is a high vulnerability published on June 8, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: fix access to stale wptr mapping Use drm_exec to take both locks i.e vm root bo and wptr_obj bo to access the mapping data properly. This fixes the security issue of unmap the wptr_obj while a queue creation is in…
When was CVE-2026-46311 disclosed?
CVE-2026-46311 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46311 actively exploited?
CVE-2026-46311 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 98.5% of all scored CVEs.
What is the CVSS score of CVE-2026-46311?
CVE-2026-46311 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46311?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46311, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46311

Explore →

Is Your Infrastructure Affected by CVE-2026-46311?

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

Start Free Scan →Browse All CVEs