Security Advisory

CVE-2024-57255: U-Boot SquashFS Symlink Overflow

Last updated:
  • CVE-2024-57255

CVE-2024-57255 is an integer overflow in the SquashFS driver of the U-Boot bootloader before 2025.01-rc1: a crafted symlink with an inode size of 0xffffffff wraps an allocation to zero bytes, and the following copy overwrites memory. NVD scores it 6.8. On verified boot devices this can break the chain of trust; v2025.01-rc1 fixes it.

Vulnerability summary

CVSS base score

6.8

Medium severity

EPSS score (FIRST)

0.4%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2024-57255 · Source: NVD

Affected components

ComponentCPEVersion range
Das U-Boot bootloader, SquashFS driver (sqfs_resolve_symlink)cpe:2.3:a:denx:u-boot:*:*:*:*:*:*:*:*Up to and including 2024.10 (NVD); fixed in v2025.01-rc1, first release 2025.01 (sigma star advisory). Only builds with FS_SQUASHFS enabled
Debian u-boot packagepkg:deb/debian/u-bootbullseye fixed in 2021.01+dfsg-5+deb11u1 (DLA-4150-1, 2025-05-01); bookworm fixed in 2023.01+dfsg-2+deb12u2; unstable fixed in 2025.01-1; trixie fixed (Debian security tracker, as of 2026-11-20)
Buildroot boot/uboot (default 'latest version')—2024.10 in Buildroot 2024.11 to 2024.11.4 and 2024.01 in 2024.02.x, with no patches; 2025.01 from Buildroot 2025.02 (commit 6ff1a66e). Boards that pin their own U-Boot version need a separate check
Yocto Project poky meta/recipes-bsp/u-boot—kirkstone (2022.01) and scarthgap (2024.01) carry a backported CVE-2024-57255.patch; walnascar builds 2025.01 (fixed); styhead builds 2024.07 with no patch (as of 2026-11-20)

What does this mean for affected devices?

CVE-2024-57255 is an integer overflow in the SquashFS driver of the U-Boot bootloader, in the function that resolves symlink targets. NVD's description reads: "An integer overflow in sqfs_resolve_symlink in Das U-Boot before 2025.01-rc1 occurs via a crafted squashfs filesystem with an inode size of 0xffffffff, resulting in a malloc of zero and resultant memory overwrite." The record was published on 2025-02-18 by MITRE as CNA (NVD, CVE record).

What does the fix commit change?

When U-Boot follows a SquashFS symlink, sqfs_resolve_symlink() copies the link target into a new buffer and adds a terminating null byte. It read the 32-bit symlink_size from the image and called malloc(sz + 1). The fix commit 233945eb by Richard Weinberger, reviewed by Miquel Raynal, explains the effect: "A carefully crafted squashfs filesystem can exhibit an inode size of 0xffffffff, as a consequence malloc() will do a zero allocation. Later in the function the inode size is again used for copying data. So an attacker can overwrite memory." The fix computes the size with __builtin_add_overflow(), returns NULL on overflow, and adjusts the null terminator and strncpy() length to the checked size. GitHub's compare view shows the commit is in tag v2025.01-rc1 and not in v2024.10. It is the SquashFS counterpart of the ext4 bug CVE-2024-57256.

Where does the report come from?

Richard Weinberger and David Gstir of sigma star gmbh published advisory sigma-star-sa-2024-002 on oss-security on 2025-02-17. It covers six CVEs, CVE-2024-57254 to CVE-2024-57259, in U-Boot 2024.10 and earlier, with v2025.01-rc1 as the fixed version. Three of them are in SquashFS symlink handling: this one, CVE-2024-57254 and the stack overflow CVE-2024-57257. The impact statement is the same for all six: "An attacker capable of modifying ext4 or SquashFS filesystem data structures can exploit multiple memory corruption vulnerabilities in U-Boot. For systems that rely on verified boot, these vulnerabilities allow an attacker to bypass the chain of trust and achieve code execution".

How severe is CVE-2024-57255?

NVD's Primary score is CVSS v3.1 6.8 (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). MITRE's CNA score is 7.1 (AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), with higher attack complexity but a changed scope. The weakness is CWE-190, Integer Overflow or Wraparound, as listed by MITRE. NVD's CPE covers denx:u-boot up to and including 2024.10. The physical attack vector reflects the precondition: someone has to place a crafted SquashFS image on storage that U-Boot reads, such as an SD card, eMMC partition, NAND volume or USB drive. On a product that relies on verified boot, that is exactly the attacker verified boot is meant to stop.

Which firmware builds carry it?

Any U-Boot older than v2025.01-rc1 without the backport, built with SquashFS support. In U-Boot's Kconfig, FS_SQUASHFS ("Enable SquashFS filesystem support") has no default and is selected by CMD_SQUASHFS, so a build without SquashFS does not contain the vulnerable code. No device vendor or CISA advisory names products for this CVE as of 2026-11-20. Siemens SSA-577017 covers the sibling CVEs CVE-2024-57256 and CVE-2024-57258 in RUGGEDCOM ROX devices, but its CISA CSAF republication (ICSA-26-134-16) does not list CVE-2024-57255. Downstream status:

  • Debian fixed bullseye in 2021.01+dfsg-5+deb11u1 with DLA-4150-1 (2025-05-01, covering all six sigma star CVEs plus several 2022 U-Boot CVEs), bookworm in 2023.01+dfsg-2+deb12u2 and unstable in 2025.01-1 (Debian security tracker, as of 2026-11-20).
  • Buildroot's default U-Boot ("latest version") was 2024.10 in Buildroot 2024.11 through 2024.11.4, and 2024.01 in the 2024.02.x branch through 2024.02.13, with no patches in boot/uboot. The bump to 2025.01 of 2025-01-17 shipped in Buildroot 2025.02. Board configs that pin their own U-Boot version or a vendor fork need their own check.
  • Yocto Project: the poky scarthgap branch (U-Boot 2024.01) and kirkstone branch (U-Boot 2022.01) carry CVE-2024-57255.patch, a backport of commit 233945eb. Walnascar builds U-Boot 2025.01, which includes the fix. Styhead builds 2024.07 with no CVE patches in the recipe, as of 2026-11-20. Vendor BSP layers often replace the poky recipe.

How do you fix CVE-2024-57255?

Rebuild on U-Boot v2025.01-rc1 or later (2025.01 is the first release), or apply commit 233945eb (denx mirror) to your fork. Backport the other five sigma star fixes with it. If the product does not need to read SquashFS in the bootloader, disable CMD_SQUASHFS and FS_SQUASHFS, and avoid reading any file system from writable media before signature verification. Our U-Boot security guide explains how to match the 2024 file system CVEs to a build, and the memory corruption fix guide covers the integer overflow class. An earlier SquashFS write flaw in the same driver is CVE-2022-33103; other U-Boot pages include CVE-2022-34835 and CVE-2021-27097.

Is CVE-2024-57255 exploited?

It is not in the CISA KEV catalog as of 2026-11-20 (catalog version 2026.11.18, 1,786 entries). FIRST EPSS gives it 0.00369, the 31.4th percentile, in the 2026-11-19 dataset (CISA KEV, FIRST EPSS). CISA's ADP SSVC entry in the NVD record marks exploitation as "none" and automatable as "no".

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • NVD (read 2026-11-20): status Modified; published 2025-02-18; sqfs_resolve_symlink integer overflow in U-Boot before 2025.01-rc1; NVD Primary CVSS v3.1 6.8 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; MITRE Secondary 7.1 CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H; CWE-190 (MITRE); CPE denx:u-boot up to and including 2024.10; CISA ADP SSVC exploitation none, automatable no. — NVD
  • CVE.org API (read 2026-11-20): state PUBLISHED, CNA MITRE, CNA CVSS v3.1 7.1, CWE-190; references denx commit 233945eb and oss-security 2025/02/17/2. — CVE.org
  • sigma-star-sa-2024-002 (2025-02-17, Richard Weinberger and David Gstir) (read 2026-11-20): CVE-2024-57254 to 57259, affected <= 2024.10, fixed v2025.01-rc1; CVE-2024-57255 is an integer overflow in U-Boot's SquashFS symlink resolution function; attacker modifying ext4 or SquashFS structures can bypass the chain of trust on verified boot systems. — oss-security (sigma star)
  • U-Boot commit 233945eb (Richard Weinberger, authored 2024-08-02, committed 2024-08-15, reviewed by Miquel Raynal) (read 2026-11-20): an inode size of 0xffffffff makes malloc() do a zero allocation, and the size is later used for copying, so an attacker can overwrite memory; fixed with __builtin_add_overflow() before malloc(). GitHub compare shows the commit contained in v2025.01-rc1 and not in v2024.10. — U-Boot commit 233945eb
  • Debian security tracker (read 2026-11-20): bullseye fixed in 2021.01+dfsg-5+deb11u1 (DLA-4150-1), bookworm 2023.01+dfsg-2+deb12u2, unstable 2025.01-1 (bug 1098254); trixie 2025.01-3+deb13u1 fixed. — Debian security tracker
  • DLA-4150-1 (Daniel Leidert, 2025-05-01) (read 2026-11-20): u-boot 2021.01+dfsg-5+deb11u1 for Debian 11 bullseye fixes CVE-2024-57254 to 57259 plus CVE-2019-14196, CVE-2022-2347, CVE-2022-30552, CVE-2022-30767, CVE-2022-30790, CVE-2022-33103, CVE-2022-33967, CVE-2022-34835. — Debian LTS DLA-4150-1
  • Buildroot (read 2026-11-20): commit 6ff1a66e (2025-01-17) bumps the default U-Boot to 2025.01; tags 2025.02 and 2025.02-rc1 default to 2025.01; tags 2024.11 to 2024.11.4 default to 2024.10 and 2024.02.12/2024.02.13 to 2024.01; boot/uboot holds only Config.in, uboot.hash and uboot.mk (no patches) in those tags. — Buildroot
  • Yocto poky (read 2026-11-20): scarthgap u-boot_2024.01.bb adds file://CVE-2024-57255.patch (SRCREV identical to v2024.01); kirkstone u-boot_2022.01.bb adds file://CVE-2024-57255.patch (Upstream-Status: Backport of 233945eb, Hongxu Jia); walnascar SRCREV identical to v2025.01; styhead u-boot_2024.07.bb with no files/ patch directory. — Yocto Project poky
  • U-Boot v2025.01 Kconfig (read 2026-11-20): FS_SQUASHFS 'Enable SquashFS filesystem support' has no default; CMD_SQUASHFS selects FS_SQUASHFS. — U-Boot fs/squashfs/Kconfig
  • CISA CSAF ICSA-26-134-16 (Siemens SSA-577017, RUGGEDCOM ROX) (read 2026-11-20) lists CVE-2024-57256 and CVE-2024-57258, not CVE-2024-57255. — CISA ICSA-26-134-16 (CSAF)
  • Not in the CISA KEV catalog as of 2026-11-20 (catalog version 2026.11.18, 1,786 entries) (read 2026-11-20). — CISA KEV
  • EPSS 0.00369, percentile 0.31372 (31.4th), dataset 2026-11-19 (read 2026-11-20). — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CVE.org record CVE-2024-57255 (CNA: MITRE)
  3. oss-security: Multiple Vulnerabilities in U-Boot (sigma star, sigma-star-sa-2024-002)
  4. U-Boot commit 233945eb: squashfs: Fix integer overflow in sqfs_resolve_symlink()
  5. U-Boot commit 233945eb (source.denx.de)
  6. Debian security tracker: CVE-2024-57255
  7. Debian LTS Advisory DLA-4150-1: u-boot security update
  8. Buildroot commit 6ff1a66e: boot/uboot: bump to version 2025.01
  9. Yocto Project poky (scarthgap): u-boot recipe patches
  10. Yocto Project poky (kirkstone): u-boot recipe patches
  11. U-Boot v2025.01 fs/squashfs/Kconfig
  12. CISA ICSA-26-134-16: Siemens Ruggedcom Rox (CSAF, lists the sibling CVEs)
  13. CISA KEV
  14. FIRST EPSS

Frequently asked questions

Which U-Boot version fixes CVE-2024-57255?

v2025.01-rc1, so U-Boot 2025.01 is the first release with the fix (commit 233945eb). NVD lists 2024.10 and earlier as affected. Debian backported it to bullseye in 2021.01+dfsg-5+deb11u1 (DLA-4150-1) and to bookworm in 2023.01+dfsg-2+deb12u2.

How is CVE-2024-57255 exploited, and who is exposed?

An attacker has to supply a crafted SquashFS image with a symlink of size 0xffffffff that U-Boot resolves, for example on an SD card, eMMC, NAND or USB stick, which is why NVD uses a physical attack vector. The result is a heap overwrite in the bootloader; on a verified boot system the sigma star advisory says this can bypass the chain of trust. Builds without FS_SQUASHFS are not exposed.

Is a Buildroot or Yocto build affected by CVE-2024-57255?

It depends on the branch and board. Buildroot's default U-Boot is fixed from Buildroot 2025.02 (U-Boot 2025.01); 2024.11.x and 2024.02.x ship older U-Boot with no patch. Yocto poky kirkstone and scarthgap carry a backported CVE-2024-57255.patch, walnascar builds 2025.01, and styhead's 2024.07 recipe has no patch, as of 2026-11-20. Board-specific U-Boot forks need their own check.

Is CVE-2024-57255 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-20 (catalog version 2026.11.18, 1,786 entries). FIRST EPSS gives it 0.00369, the 31.4th percentile, in the 2026-11-19 dataset.