CVE-2024-0607
Linux Kernel ≤ 6.7
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-0607 is a medium-severity Improper Handling of Values (CWE-229) vulnerability in Linux Linux Kernel. Its CVSS base score is 6.6 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 14th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-16400
Vulnerability Data
A flaw was found in the Netfilter subsystem in the Linux kernel. The issue is in the nft_byteorder_eval() function, where the code iterates through a loop and writes to the `dst` array. On each iteration, 8 bytes are written, but…
more
`dst` is an array of u32, so each element only has space for 4 bytes. That means every iteration overwrites part of the previous element corrupting this array of u32. This flaw allows a local user to cause a denial of service or potentially break NetFilter functionality.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly enforces correct handling of parameter counts and defined values before processing occurs.
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 require proper input validation and parameter handling to prevent this 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.
Secure development lifecycle includes input validation and parameter handling requirements that reduce missing-value errors.
A.8.26 requires identifying and specifying requirements (incl. input validation, resilience against SQLi/buffer overflows, integrity checks) that can address improper value handling during development, but this is only a minority slice of CWE-229's broad class of value-count/undefined cases across all input and parameter sites.
A.8.27 mandates security-by-design principles (e.g. distrust input, least privilege, fail securely, data validation/sanitization) and design reviews that can stop improper value handling from reaching production in many cases, but leaves a bounded remainder (e.g. legacy code, outsourced development where principles are only contractually required, or incomplete application of the full set of principles).
Secure coding standards mandate proper handling of missing or undefined parameters, directly addressing this weakness.