Cyber Resilience

CVE-2026-46309

Linux Kernel 6.18 – 6.18.32

Published
08 June 2026
Modified
15 July 2026
Patch / advisory
CVSS Score v3.1 7.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0013 3th percentile
Risk Priority 49 floored blend · peak EPSS

Summary

CVE-2026-46309 is a high-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Linux Linux Kernel. Its CVSS base score is 7.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-39948Same product: Linux Linux Kernel
CVE-2026-45964Same product: Linux Linux Kernel
CVE-2026-45941Same product: Linux Linux Kernel
CVE-2024-44971Same product: Linux Linux Kernel
CVE-2026-46207Same product: Linux Linux Kernel
CVE-2026-53113Same product: Linux Linux Kernel
CVE-2024-38563Same product: Linux Linux Kernel
CVE-2024-56572Same product: Linux Linux Kernel
CVE-2024-50254Same product: Linux Linux Kernel
CVE-2023-52936Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
7.1 · 6.18 — 6.18.32 · 6.19 — 7.0.9

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V14.3.2

Mitigating Controls (NIST 800-53 r5) AI

Enforces access authorizations so that cached sensitive data cannot be read by actors outside the intended sphere.

Developer testing and evaluation (static analysis, fuzzing, or runtime leak detection) directly finds missing deallocation.

Directly prevents unauthorized transfer of information through shared resources such as caches.

Controls information flows to keep sensitive data from leaving its authorized control sphere via caches.

Requiring documented development standards and tools can mandate memory-management disciplines that avoid leaks at introduction.

Engineering principles applied during development can require explicit resource-release patterns that stop memory leaks from being coded.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 mostly match
prevents

Protecting confidentiality of data-at-rest covers caches that persist sensitive information.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.

PR.AA-05 partial match
prevents

Enforcing least-privilege access permissions directly limits who can read cached sensitive data.

PR.DS-10 partial match
prevents

Protecting data-in-use can mitigate exposure when caches hold transient sensitive values.

PR.IR-01 partial match
prevents

Logical access controls on environments reduce the chance an outsider can reach the cache.

PR.PS-01 partial match
prevents

Hardened configuration baselines can disable or secure caching of sensitive data.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Data leakage prevention can block unauthorized access to cached sensitive information.

finds

Security testing in development can detect unreleased memory, providing partial coverage of the weakness.

prevents

Information access restriction directly limits who can read cached sensitive data.

mitigates

Information deletion ensures sensitive data is removed from caches when no longer needed.

mitigates

Cryptography can protect cached data at rest, but does not address access control scope.

prevents

Secure development life cycle mandates memory-management practices that reduce missing-release defects.

References