CVE-2024-23981
Intel Ethernet 800 Series Controllers Driver ≤ 28.3
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-23981 is a critical-severity Wrap-around Error (CWE-128) vulnerability in Intel Ethernet 800 Series Controllers Driver. Its CVSS base score is 9.3 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); 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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-21407
Vulnerability Data
Wrap-around error in Linux kernel mode driver for some Intel(R) Ethernet Network Controllers and Adapters before version 28.3 may allow an authenticated user to potentially enable escalation of privilege via local access.
- 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 can discover wrap-around conditions through static analysis or test cases.
Requiring documented development processes and standards can enforce coding rules and tool usage that reduce introduction of calculation errors.
Security engineering principles include use of safe arithmetic constructs and bounded types that structurally avoid wrap-around.
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 wrap-around via safe arithmetic, bounds checks, and language features, but the control addresses many additional weakness classes.
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 bounds checking that can prevent wrap-around errors.
A.8.26 only requires that security requirements (including resilience against buffer overflows or SQL injections) be identified and specified during development or acquisition; it does not itself enforce, implement, or prevent wrap-around errors from being exploitable in the resulting application.
Secure architecture principles include use of safe data types and overflow detection mechanisms.
Secure coding standards directly require avoidance of integer overflow and wrap-around conditions.
Security testing can detect wrap-around errors through boundary and fuzz testing.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-682, a pillar-level weakness, and none of its children carries one either.