Skip to main content
VulnerabilityPublished Updated

CVE-2024-57259: denx U-Boot · Off-by-one Error

Affects denx U-BootSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
denx U-BootAffected
  • =0
  • =2025.01-rc1
Fixed in–

AI-suggested

To mitigate CVE-2024-57259, European organizations should prioritize updating affected U-Boot versions to 2025.01-rc1 or later once the patch is officially released. Until then, vendors and integrators should apply any available backported patches or mitigations. Organizations should conduct an inventory of embedded devices using U-Boot with SquashFS filesystem support and assess exposure. Physical security controls must be strengthened to prevent unauthorized physical access to devices, including secure facility access, tamper-evident seals, and surveillance. Implement strict supply chain security practices to ensure firmware integrity and authenticity. Network segmentation and monitoring should be enhanced to detect anomalous device behavior indicative of exploitation attempts. Additionally, organizations should engage with device manufacturers to confirm patch availability and deployment timelines. Regular firmware integrity checks and secure boot mechanisms can help detect and prevent exploitation of corrupted bootloader code.

Description

sqfs_search_dir in Das U-Boot before 2025.01-rc1 exhibits an off-by-one error and resultant heap memory corruption for squashfs directory listing because the path separator is not considered in a size calculation.

References

Community reviews

Loading reviews…