CVE-2026-46309

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.0EG
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.0Exploit: None knownExposed: 0

A fix is available — apply it.

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

drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise

Add validation in xe_vm_madvise_ioctl() to reject PAT indices with XE_COH_NONE coherency mode when applied to CPU cached memory.

Using coh_none with CPU cached buffers is a security issue. When the kernel clears pages before reallocation, the clear operation stays in CPU cache (dirty). GPU with coh_none can bypass CPU caches and read stale sensitive data directly from DRAM, potentially leaking data from previously freed pages of other processes.

This aligns with the existing validation in vm_bind path (xe_vm_bind_ioctl_validate_bo).

v2(Matthew brost)

  • Add fixes
  • Move one debug print to better place

v3(Matthew Auld)

  • Should be drm/xe/uapi
  • More Cc

v4(Shuicheng Lin)

  • Fix kmem leak issues by the way

v5

  • Remove kmem leak because it has been merged by another patch

v6

  • Remove the fix which is not related to current fix

v7

  • No change

v8

  • Rebase

v9

  • Limit the restrictions to iGPU

v10

  • No change

(cherry picked from commit 016ccdb674b8c899940b3944952c96a6a490d10a)

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity70% × 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

July 23, 2026

Advisory Details (6)

Auto-updated Jul 2, 2026
Patch available. Sources: redhat.
redhat

2486468 – (CVE-2026-46309) CVE-2026-46309 kernel: drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise

https://bugzilla.redhat.com/show_bug.cgi?id=2486468
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-46309
generic

drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87f9b1528e1ffc1da3615d552c9a06aba5e20b00
generic

drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e5591c2fc1b30f4ea5e2eab4c3a695acc404e39

Vendor Advisories for CVE-2026-46309(1)

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

Patch Availability(8)

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 (135 versions)7.0.9-1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 23× in last 7d / 129× 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 220 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46309?
CVE-2026-46309 is a high vulnerability published on June 8, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise Add validation in xevmmadvise_ioctl() to reject PAT indices with XECOHNONE coherency mode when applied to CPU cached memory. Using coh_none with CPU cached…
When was CVE-2026-46309 disclosed?
CVE-2026-46309 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46309 actively exploited?
CVE-2026-46309 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46309?
CVE-2026-46309 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-46309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46309, 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-46309

Explore →

Is Your Infrastructure Affected by CVE-2026-46309?

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