Raw vector
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/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-57262 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Pengutronix (inferred from references). Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 20th 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-2024-57262 is an integer overflow vulnerability in the ext4fs_read_symlink function of barebox, affecting versions prior to 2025.01.0. The issue occurs when processing a crafted ext4 filesystem with an inode size of 0xffffffff, an le32 variable. Adding one to this value triggers an overflow in the zalloc call, resulting in a malloc of zero bytes and a subsequent memory overwrite. This flaw is classified under CWE-190 (Integer Overflow or Wraparound) and carries a CVSS v3.1 base score of 7.1.
Exploitation requires physical access to the target system (AV:P) and involves high attack complexity (AC:H), with no privileges (PR:N) or user interaction (UI:N) needed. Successful exploitation changes scope (S:C) and can lead to high confidentiality, integrity, and availability impacts (C:H/I:H/A:H), primarily through the memory overwrite enabled by the zero-sized allocation.
Mitigation is addressed in barebox version 2025.01.0 via patches documented in the project's Git repository, specifically commits a2b76550f7d8 and a2b76550f7d87ba6f88a9ea50e71f107b514ff4e, which fix the integer overflow in ext4fs_read_symlink. Security practitioners should update to barebox 2025.01.0 or later and validate ext4 filesystems from untrusted sources.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4759
Vulnerability Data
In barebox before 2025.01.0, ext4fs_read_symlink has an integer overflow for zalloc (adding one to an le32 variable) via a crafted ext4 filesystem with an inode size of 0xffffffff, resulting in a malloc of zero and resultant memory overwrite, a related…
more
issue to CVE-2024-57256.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.
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 use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
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 integer overflows before release.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.