Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46309: drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 4e5591c2fc1b30f4ea5e2eab4c3a695acc404e39, 87f9b1528e1ffc1da3615d552c9a06aba5e20b00, fea04cf6f2345bc50f15b6638906c35962b89424.

Low priority for now. Upgrade to Linux Linux 4e5591c2fc1b30f4ea5e2eab4c3a695acc404e39, 87f9b1528e1ffc1da3615d552c9a06aba5e20b00, fea04cf6f2345bc50f15b6638906c35962b89424 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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)

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Jun 8, 2026
Updated
Jul 23, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46309

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.18 and later · before 6.18.32
  • linux linux kernel6.19 and later · before 7.0.9
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.18affected
    • ada7486c5668db542a7d361268df931aca5b726a and later · before 87f9b1528e1ffc1da3615d552c9a06aba5e20b00affected · git
    • ada7486c5668db542a7d361268df931aca5b726a and later · before fea04cf6f2345bc50f15b6638906c35962b89424affected · git
    • ada7486c5668db542a7d361268df931aca5b726a and later · before 4e5591c2fc1b30f4ea5e2eab4c3a695acc404e39affected · git
    • before 6.18not affected · semver
    • 6.18.32 and later · up to and including 6.18.*not affected · semver
    • 7.0.9 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-corebefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-debugbefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-debug-corebefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
AlmaLinux:9kernel-debug-modules-extrabefore 5.14.0-687.57.1.el9_85.14.0-687.57.1.el9_8
Debian:14linuxbefore 7.0.9-17.0.9-1
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-687.57.1.el9_80:5.14.0-687.57.1.el9_8
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-687.57.1.el9_80:5.14.0-687.57.1.el9_8
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-687.57.1.el9_80:5.14.0-687.57.1.el9_8
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-687.57.1.el9_80:5.14.0-687.57.1.el9_8
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-687.57.1.el9_80:5.14.0-687.57.1.el9_8

+85

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-46305Jun 8, 2026 · staging: rtl8723bs: os_dep: avoid NULL pointer dereference in rtw_cbuf_alloc
    22Monitor
  • ← EarlierCVE-2026-46308Jun 8, 2026 · pmdomain: mediatek: fix use-after-free in scpsys_get_bus_protection_legacy()
    31Monitor
  • Later →CVE-2026-46310Jun 8, 2026 · media: renesas: vsp1: Fix NULL pointer deref on module unload
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4e5591c2fc1b30f4ea5e2eab4c3a695acc404e39Vendor (CNA)
Linux Linux87f9b1528e1ffc1da3615d552c9a06aba5e20b00Vendor (CNA)
Linux Linuxfea04cf6f2345bc50f15b6638906c35962b89424Vendor (CNA)
almalinux:kernel5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules-core5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules-extra5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists5.14.0-687.57.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux7.0.9-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-687.57.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-687.57.1.el9_8 · Rocky Linux:9Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records