Kernel memory exhaustion via failed Lima mappings
Published May 17, 2024 · Updated May 11, 2026
Memory leak in the Lima DRM heap allocator in Linux 5.7 and later affected branches allows local users to exhaust kernel memory. On a lima_vm_map_bo failure, lima_heap_alloc returns without unmapping the DMA scatter-gather table or freeing the table and its stored pointer. Low-privileged access to the Lima DRM interface is required, and repeated failed mappings can interrupt service through unreclaimed memory.
Summary
What happened
Memory leak in the Lima DRM heap allocator in Linux 5.7 and later affected branches allows local users to exhaust kernel memory. On a lima_vm_map_bo failure, lima_heap_alloc returns without unmapping the DMA scatter-gather table or freeing the table and its stored pointer. Low-privileged access to the Lima DRM interface is required, and repeated failed mappings can interrupt service through unreclaimed memory.
The record
- CVE
- CVE-2024-35829
- Published
- May 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 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=5.7
- Affected versionversion=6aebc51d7aeff5a30d86485f320f0c871b5f23a4 <04ae3eb470e52a3c41babe85ff8cee195e4dcbea
- Affected versionversion=6aebc51d7aeff5a30d86485f320f0c871b5f23a4 <4ab14eccf5578af1dd5668a5f2d771df27683cab
- Affected versionversion=6aebc51d7aeff5a30d86485f320f0c871b5f23a4 <746606d37d662c70ae1379fc658ee9c65f06880f
- Affected versionversion=6aebc51d7aeff5a30d86485f320f0c871b5f23a4 <8e25c0ee5665e8a768b8e21445db1f86e9156eb7
- Affected versionversion=6aebc51d7aeff5a30d86485f320f0c871b5f23a4 <ec6bb037e4a35fcbb5cd7bc78242d034ed893fcd
- Affected versionversion=6aebc51d7aeff5a30d86485f320f0c871b5f23a4 <f2e80ac9344aebbff576453d5c0290b332e187ed
- Affected versionversion=6aebc51d7aeff5a30d86485f320f0c871b5f23a4 <f6d51a91b41704704e395de6839c667b0f810bbf
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