VulnerabilityPublished 19 Feb 2025Updated 3 Nov 2025

CVE-2024-57257: sqfs_size · Stack Consumption Issue

Source GCVE Database

Compare

Authoritative record:CVE-2024-57257· Low 2.0

Not known to be exploited · CVSS 2.0 Low · fixed in 2025.01-rc1 : update Das U-Boot when convenient.

Data as of 30 Oct 2026, 01:11 UTC

CVSS 3.1 base score

2.0Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (mitre)	CVSS 3.1	2.0

Affects: Das U-Boot before 2025.01
Patch: Available – fixed in 2025.01-rc1

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

Attack Vector: Physical
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-8h8c-f86r-pf3c

What to do

AI-suggested

A fix is available in Das U-Boot version 2025.01-rc1 and later. Users should upgrade to this version or a later release to remediate the issue. No other mitigation or workaround is indicated.

Description

CVE-2024-57257 is a low severity vulnerability in Das U-Boot before version 2025.01-rc1. It involves a stack consumption issue in the sqfs_size function triggered by a crafted squashfs filesystem with deep symlink nesting. This flaw does not impact confidentiality or integrity but may cause a denial of service due to resource exhaustion.

Impact

The vulnerability can lead to denial of service by exhausting stack resources during filesystem processing. There is no impact on confidentiality or integrity. Exploitation requires physical access and is complex, limiting practical risk.

Summary

This vulnerability in Das U-Boot's sqfs_size function arises from excessive stack consumption when processing a specially crafted squashfs filesystem containing deeply nested symbolic links. The issue affects all versions prior to 2025.01-rc1. The CVSS v3.1 base score is 2.0, reflecting low impact with attack vector requiring physical access (AV:P), high attack complexity (AC:H), no privileges required (PR:N), no user interaction (UI:N), and only availability impact (A:L). No known exploits are reported in the wild.

CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Oct 2026, 01:11 UTC

WeaknessesCWE-674

Technical details

References

Community reviews

Related threats