Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HCVSS 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-31631 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Linux Kernel. Its CVSS base score is 8.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation of Remote Services (T1210); ranked at the 32th 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-31631 is a buffer overread vulnerability in the Linux kernel's rxrpc subsystem, specifically within the rxgk_do_verify_authenticator() function. The flaw occurs because the function fails to check the buffer size before accessing the nonce, potentially allowing reads beyond the allocated buffer boundaries. This issue affects the Linux kernel and is classified under CWE-787 (Out-of-bounds Write), with a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H). The vulnerability was published on 2026-04-24.
Remote attackers can exploit this vulnerability over the network with low attack complexity, requiring no privileges, user interaction, or special conditions. Successful exploitation results in low confidentiality impact, such as limited exposure of sensitive data, and high availability impact, typically manifesting as kernel crashes or denial of service.
Mitigation requires updating to a patched Linux kernel version that includes the fixes from the referenced stable commits: https://git.kernel.org/stable/c/1c4422d8be81718ecb15d79aedff607323085201, https://git.kernel.org/stable/c/794586789800b16dcbe235452494f4223ac80413, and https://git.kernel.org/stable/c/f564af387c8c28238f8ebc13314c589d7ba8475d. These patches add the necessary buffer size check before nonce verification in rxgk_do_verify_authenticator().
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25524
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix buffer overread in rxgk_do_verify_authenticator() Fix rxgk_do_verify_authenticator() to check the buffer size before checking the nonce.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
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.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
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.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.