Code execution via wrapped symlink allocation
Published Feb 19, 2025 · Updated Feb 19, 2025
Memory corruption in Pengutronix barebox before 2025.01.0 allows physically proximate attackers to execute code via a crafted ext4 filesystem. The ext4fs_read_symlink function adds one to an untrusted 32-bit inode size before passing it to zalloc; 0xffffffff wraps to zero, so later symlink copying overwrites memory. Exploitation requires control of filesystem data parsed during boot and can bypass a verified-boot chain.
Summary
What happened
Memory corruption in Pengutronix barebox before 2025.01.0 allows physically proximate attackers to execute code via a crafted ext4 filesystem. The ext4fs_read_symlink function adds one to an untrusted 32-bit inode size before passing it to zalloc; 0xffffffff wraps to zero, so later symlink copying overwrites memory. Exploitation requires control of filesystem data parsed during boot and can bypass a verified-boot chain.
The record
- CVE
- CVE-2024-57262
- Published
- Feb 19, 2025
- Updated
- Feb 19, 2025
- Vendor
- Pengutronix
- Product
- barebox
- Classifications
- CWE-190
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2025.01.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo