UML startup termination via signed map-size overflow
Published Dec 24, 2024 · Updated May 11, 2026
Integer overflow in Linux kernel 4.1 through 6.12.1 allows local users to terminate a UML/i386 instance during physical-memory setup. setup_physmem stores the unsigned len-minus-reserve result in a signed long, so values above LONG_MAX become negative and trigger the too-little-memory exit path. Exploitation requires local control of an i386 User-Mode Linux launch with an oversized physical-memory map and interrupts only that UML instance.
Summary
What happened
Integer overflow in Linux kernel 4.1 through 6.12.1 allows local users to terminate a UML/i386 instance during physical-memory setup. setup_physmem stores the unsigned len-minus-reserve result in a signed long, so values above LONG_MAX become negative and trigger the too-little-memory exit path. Exploitation requires local control of an i386 User-Mode Linux launch with an oversized physical-memory map and interrupts only that UML instance.
The record
- CVE
- CVE-2024-53145
- Published
- Dec 24, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-190, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=4.1
- Affected versionversion=fe205bdd1321f95f8f3c35d243ea7cb22af8fbe1 <1575df968650d11771359e5ac78278c5b0cc19f3
- Affected versionversion=fe205bdd1321f95f8f3c35d243ea7cb22af8fbe1 <1bd118c5f887802cef2d9ba0d1917258667f1cae
- Affected versionversion=fe205bdd1321f95f8f3c35d243ea7cb22af8fbe1 <5c710f45811e7e2bfcf703980c306f19c7e1ecfe
- Affected versionversion=fe205bdd1321f95f8f3c35d243ea7cb22af8fbe1 <a875c023155ea92b75d6323977003e64d92ae7fc
- Affected versionversion=fe205bdd1321f95f8f3c35d243ea7cb22af8fbe1 <a98b7761f697e590ed5d610d87fa12be66f23419
- Affected versionversion=fe205bdd1321f95f8f3c35d243ea7cb22af8fbe1 <a9c95f787b88b29165563fd97761032db77116e7
- Affected versionversion=fe205bdd1321f95f8f3c35d243ea7cb22af8fbe1 <d1a211e5210d31da8f49fc0021bf7129b726468c
- Affected versionversion=fe205bdd1321f95f8f3c35d243ea7cb22af8fbe1 <e6102b72edc4eb8c0858df00ba74b5ce579c8fa2
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