Security Resilience

CVE-2026-31470

Memory Safety in Linux Kernel 6.7 – 6.12.80

Published
22 April 2026
Modified
19 October 2026
Patch / advisory
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS Score 0.0013 2th percentile
Risk Priority 50 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-31470 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Linux Kernel. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation of Remote Services (T1210); ranked at the 2th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-31470 is a vulnerability in the Linux kernel's TDX guest module, which handles Intel Trust Domain Extensions (TDX) environments for confidential computing and remote attestation. The issue stems from improper validation of the host-controlled `quote_buf->out_len` value, which dictates the number of bytes copied from the attestation quote buffer to guest userspace. Without proper checks, this allows the guest to copy data beyond its allocated pages—up to the TSM_REPORT_OUTBLOB_MAX limit—potentially exposing unintended memory contents. Quotes in TDX are not private and can be forwarded to attestation servers.

A local attacker with low privileges (PR:L) on the affected TDX guest system can exploit this vulnerability with low complexity (AC:L) and no user interaction (UI:N). By triggering quote generation or consumption via interfaces like per-container configs-tsm-report, the attacker can cause the guest to read out-of-bounds data based on a maliciously large `quote_buf->out_len` set by the host, or exploit races during response modification. This results in high confidentiality impact (C:H) through memory leaks that may cross container boundaries, and high availability impact (A:H) from potential crashes or denial of service, all within the guest's unchanged scope (S:U).

Mitigation requires applying kernel patches from the referenced stable commits, including 02ca2d9d197723696cb9cc0cb159eb7e8bf5f89b, 6f3c8795ae9ba74fa10fe979293d1904712d3fb1, a079a62883e3365de592cea9f7a669d8115433b0, and c3fd16c3b98ed726294feab2f94f876290bf7b61. These fixes add validation for the host-controlled length and handle races, preventing excessive copies to userspace. Security practitioners should update TDX guest kernels promptly, especially in multi-tenant or containerized deployments.

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: virt: tdx-guest: Fix handling of host controlled 'quote' buffer length Validate host controlled value `quote_buf->out_len` that determines how many bytes of the quote are copied out to guest userspace. In…

more

TDX environments with remote attestation, quotes are not considered private, and can be forwarded to an attestation server. Catch scenarios where the host specifies a response length larger than the guest's allocation, or otherwise races modifying the response while the guest consumes it. This prevents contents beyond the pages allocated for `quote_buf` (up to TSM_REPORT_OUTBLOB_MAX) from being read out to guest userspace, and possibly forwarded in attestation requests. Recall that some deployments want per-container configs-tsm-report interfaces, so the leak may cross container protection boundaries, not just local root.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
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.
T1584.008 Network Devices Resource Development
Adversaries may compromise third-party network devices that can be used during targeting.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-21687Same product: Linux Linux Kernel
CVE-2024-53193Same product: Linux Linux Kernel
CVE-2025-21869Same product: Linux Linux Kernel
CVE-2023-52495Same product: Linux Linux Kernel
CVE-2024-26730Same product: Linux Linux Kernel
CVE-2023-52790Same product: Linux Linux Kernel
CVE-2024-50203Same product: Linux Linux Kernel
CVE-2023-52916Same product: Linux Linux Kernel
CVE-2024-38621Same product: Linux Linux Kernel
CVE-2023-31436Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
7.0 · 6.7 — 6.12.80 · 6.13 — 6.18.21 · 6.19 — 6.19.11

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.

Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.

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.PS-06 mostly match
blocks

Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

ID.RA-01 partial match
blocks

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
blocks

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

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.

finds

Security testing in development and acceptance can detect and prevent out-of-bounds write defects.

prevents

Secure coding directly addresses out-of-bounds writes through language choice and coding standards.

References