Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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-31609 is a critical-severity Double Free (CWE-415) vulnerability in Linux Kernel. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation of Remote Services (T1210); ranked at the 39th 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-8 (Security and Privacy Engineering Principles) — 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-31609 is a double-free vulnerability (CWE-415) in the Linux kernel's SMB client implementation. The issue arises because smbd_send_batch_flush() already invokes smbd_free_send_io(), but the function is called again after smbd_post_send() relocates the structure to the batch list, potentially leading to memory corruption. It affects Linux kernel versions prior to the application of the relevant stable patches and carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Remote attackers with network access can exploit this vulnerability without authentication, privileges, or user interaction due to its low attack complexity and unchanged scope. Successful exploitation could result in high-impact confidentiality, integrity, and availability violations, such as arbitrary code execution, denial of service, or data tampering via crafted SMB traffic to a vulnerable kernel's SMB client.
Mitigation involves updating to Linux kernel versions incorporating the upstream fixes, as detailed in the following stable branch commit references: https://git.kernel.org/stable/c/22b7c1c619d808aec4cad3dc42103345e370d107, https://git.kernel.org/stable/c/27b7c3e916218b5eb2ee350211140e961bfc49be, https://git.kernel.org/stable/c/a9940dcbe5cb92482c04efc7341039ddf7dbf607, and https://git.kernel.org/stable/c/f9a162c2bbcd0ac85bd07c5b37cf20286048b65c.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25502
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: smb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush() smbd_send_batch_flush() already calls smbd_free_send_io(), so we should not call it again after smbd_post_send() moved it to the batch list.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation explicitly includes dynamic analysis and fuzzing that locate double-free defects before release.
Security engineering principles can require memory-safe allocation patterns or language features that structurally eliminate double-free opportunities.
Flaw remediation processes require identification and correction of memory-management defects such as double free once discovered.
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 SDLC practices directly prevent double-free errors via static analysis, safe memory APIs, and testing.
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 can detect double-free conditions before release.
Secure coding standards directly address proper use of free() and similar functions.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248590 OL 8 must clear the page allocator to prevent use-after-free attacks. blocks CWE-415