cve.bz

CVE-2024-57258 denx u-boot: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.8 highEPSS 0.2%Fix available

High (7.8) in denx u-boot. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Integer overflows in memory allocation in Das U-Boot before 2025.01-rc1 occur for a crafted squashfs filesystem via sbrk, via request2size, or because ptrdiff_t is mishandled on x86_64.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-02-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-57258 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-57258?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-57258?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-57258 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
denx U-Bootbefore 2025.01-rc1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11u-boot2021.01+dfsg-5+deb11u1DLA-4150-1
Debian12u-boot2023.01+dfsg-2+deb12u2DEBIAN-CVE-2024-57258
Debian13, 14u-boot2025.01-1DEBIAN-CVE-2024-57258
Ubuntu22.04:LTSu-boot2022.01+dfsg-2ubuntu2.7UBUNTU-CVE-2024-57258 USN-8056-1
Ubuntu22.04:LTS, 24.04:LTSu-boot-nezhano fix listedUBUNTU-CVE-2024-57258
Ubuntu24.04:LTSu-boot2025.10-0ubuntu0.24.04.2UBUNTU-CVE-2024-57258 USN-8056-1
UbuntuPro:16.04:LTS, Pro:18.04:LTS, Pro:20.04:LTSu-bootno fix listedUBUNTU-CVE-2024-57258
SUSELinux Enterprise Micro 5.2u-boot-rpiarm642021.01-150300.7.24.1SUSE-SU-2025:0817-1
SUSELinux Enterprise Micro 5.3, Linux Enterprise Micro 5.4, Linux Enterprise Micro 5.5u-boot-rpiarm642021.10-150400.4.14.1SUSE-SU-2025:0763-1
SUSELinux Enterprise Module for Basesystem 15 SP6u-boot, u-boot-rpiarm642021.10-150600.11.3.1SUSE-SU-2025:0989-1
SUSELinux Micro 6.0u-boot-rpiarm642023.04-2.1SUSE-SU-2025:20219-1
openSUSELeap 15.6u-boot, u-boot-rpi3, u-boot-rpi4 and 39 more2021.10-150600.11.3.1SUSE-SU-2025:0989-1
openSUSELeap 15.6u-boot-xilinxzynqmpgeneric2020.01-150200.10.18.1SUSE-SU-2025:0755-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-134-16Siemens Ruggedcom Rox2026-05-12Critical ManufacturingRUGGEDCOM ROX MX5000, RUGGEDCOM ROX MX5000RE, RUGGEDCOM ROX RX1400 and 8 morenone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON