dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2024-57262

HIGH · 7.1 CVSS v3.1 Published 2025-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 issue to CVE-2024-57256.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Integer overflow in barebox's ext4fs_read_symlink function when adding 1 to an le32 variable set to 0xffffffff (max value). This causes wraparound, resulting in malloc(0) allocation and subsequent memory overwrite when processing a specially crafted ext4 filesystem with oversized inode.

MitigationUpgrade barebox to version 2025.01.0 or later. Until then, avoid mounting untrusted or unknown ext4 filesystems in barebox environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify barebox installation and version
    Run 'barebox --version' or check the barebox binary/file version. If running as a bootloader, check the version string displayed at boot or in /proc/version if available within barebox.
    Affected if The installed barebox version is earlier than 2025.01.0 (versions 2024.x and earlier are affected).
  2. Determine if ext4 filesystem support is enabled
    Check the barebox configuration file (usually .config in the build directory or /boot/config-* on the target) for CONFIG_EXT4FS=y or similar ext4-related configuration options. In running barebox, check 'help' output or available commands for ext4 support.
    Affected if CONFIG_EXT4FS or ext4fs support is compiled into the barebox binary.
  3. Verify ext4 mounting capability exists
    Check if the 'ext4' or 'mount' command with ext4 support is available in the barebox environment. Run 'help mount' or 'ls -la /boot' to see what filesystems can be mounted.
    Affected if ext4 mounting commands are available and ext4 filesystems can be mounted within barebox.
  4. Identify ext4 mount points or boot scripts
    Review any boot scripts, environment variables, or configuration files in /env or /boot that mount ext4 filesystems. Look for commands like 'mount -t ext4' or 'ext4load'. Check bootloader configuration files that specify ext4 as a rootfs or boot filesystem.
    Affected if Boot scripts or configurations mount ext4 filesystems, particularly from external or removable media.

You are affected if barebox version is earlier than 2025.01.0 AND ext4 filesystem support is enabled AND your barebox environment mounts ext4 filesystems from potentially untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade barebox to version 2025.01.0 or later. Until then, avoid mounting untrusted or unknown ext4 filesystems in barebox environments.

Recommended fix High confidence

barebox 2025.01.0 or later

  1. Obtain barebox version 2025.01.0 or later from the official barebox repository at git.pengutronix.de
  2. Verify the current barebox version installed on the target system
  3. Compile the new barebox version from source or obtain pre-built binaries for the target architecture
  4. Back up the current barebox installation and configuration
  5. Deploy the new barebox 2025.01.0 or later version to the target system
  6. Reboot the system to load the updated barebox
  7. Verify the new version is running and ext4 filesystem functionality is intact
Caveat Upgrading to a new major release may include behavioral changes; review the release notes for 2025.01.0 before deploying to production systems

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-57262 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-57262 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data