Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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-31407 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 7th 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-31407 is a vulnerability in the Linux kernel's netfilter conntrack subsystem, stemming from missing netlink policy validations for certain attributes used in SCTP and ctnetlink processing. Reported by Hyunwoo Kim, it allows out-of-bounds access, such as nlattr_to_sctp() directly assigning the user-supplied CTA_PROTOINFO_SCTP_STATE value to ct->proto.sctp.state without range validation, and invalid exp->dir values (e.g., 100) triggering slab-out-of-bounds reads up to 5600 bytes past the nf_conn object boundary, as confirmed by UBSAN.
A local attacker with low privileges (PR:L) can exploit this vulnerability with low attack complexity (AC:L) and no user interaction (UI:N) via the netlink interface. Successful exploitation enables high confidentiality impact (C:H) through information disclosure from out-of-bounds reads and high availability impact (A:H) potentially via memory corruption or denial of service, with no integrity impact (I:N) and unsynchronized scope (S:U). The CVSS v3.1 base score is 7.1.
Mitigation requires applying upstream Linux kernel patches from the stable repository, which extend netlink policies to validate the affected attributes. Key commits include 0fbae1e74493d5a160a70c51aeba035d8266ea7d, 67c53c1978cef3c504237275e39c857e2f6af56e, 9174d28f3f15d8c4962f5980c0be167633880443, c5e918390002edf0cff80a0e7ce1f86f16a9507c, and f900e1d77ee0ef87bfb5ab3fe60f0b3d8ad5ba05.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-19197
Vulnerability Data
In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: add missing netlink policy validations Hyunwoo Kim reports out-of-bounds access in sctp and ctnetlink. These attributes are used by the kernel without any validation. Extend the netlink policies…
more
accordingly. Quoting the reporter: nlattr_to_sctp() assigns the user-supplied CTA_PROTOINFO_SCTP_STATE value directly to ct->proto.sctp.state without checking that it is within the valid range. [..] and: ... with exp->dir = 100, the access at ct->master->tuplehash[100] reads 5600 bytes past the start of a 320-byte nf_conn object, causing a slab-out-of-bounds read confirmed by UBSAN.
- 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.