Security Resilience

CVE-2024-42160

Linux Kernel 4.7 – 5.15.181

Published
30 July 2024
Modified
25 March 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0024 15th percentile
Risk Priority 55 floored blend · peak EPSS

CVSS 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-2024-42160 is a high-severity Improper Check for Unusual or Exceptional Conditions (CWE-754) vulnerability in Linux Kernel. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 15th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: f2fs: check validation of fault attrs in f2fs_build_fault_attr() - It missed to check validation of fault attrs in parse_options(), let's fix to add check condition in f2fs_build_fault_attr(). - Use f2fs_build_fault_attr()…

more

in __sbi_store() to clean up code.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-35785Same product: Debian Debian Linux
CVE-2024-42159Same product: Debian Debian Linux
CVE-2025-38334Same product: Debian Debian Linux
CVE-2024-44974Same product: Debian Debian Linux
CVE-2024-35835Same product: Debian Debian Linux
CVE-2024-26698Same product: Debian Debian Linux
CVE-2024-35910Same product: Debian Debian Linux
CVE-2024-49883Same product: Debian Debian Linux
CVE-2024-27413Same product: Debian Debian Linux
CVE-2024-26702Same product: Debian Debian Linux

Affected Assets

debian
debian linux
11.0
linux
linux kernel
4.7 — 5.15.181 · 5.16 — 6.1.98 · 6.2 — 6.6.39

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation explicitly exercises unusual conditions to find missing or incorrect checks.

Input validation directly requires checking for unexpected or malformed conditions before they propagate.

Security engineering principles include structured handling of edge cases and exceptions during design.

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.

finds

Security testing in development and acceptance verifies handling of error and exceptional conditions.

finds

Monitoring may detect symptoms of unhandled conditions but does not eliminate the root weakness.

prevents

Secure coding standards directly mandate proper checks for exceptional and unusual conditions.

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-754, a class-level weakness. Rules are authored against its narrower children: CWE-354.

References