Security readout for executives and security teams
Plain-English summary
CVE-2024-35829 is a Linux kernel memory leak in the Lima DRM GPU driver. If a buffer mapping operation fails, allocated resources may not be released. The likely business impact is local denial of service from memory exhaustion on systems using the affected driver, not data theft or privilege escalation based on the supplied sources.
Executive priority
Treat this as a moderate-priority patching item. It is not reported as actively exploited and has no sourced confidentiality or integrity impact, but affected systems could suffer local availability disruption. Prioritize internet-facing appliance fleets only if they also expose local workloads or users that can reach the driver.
Technical view
The flaw is in drm/lima lima_heap_alloc. When lima_vm_map_bo fails, cleanup was missing, causing CWE-401 resource leakage. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, no confidentiality or integrity impact, high availability impact. Kernel stable commits are listed as fixes.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the Lima DRM driver present or enabled. The source bundle lists Linux as affected across kernel version entries including 5.7, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, and 6.9.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Any exploitation would require local low-privileged access and conditions that trigger the failed mapping path. The documented impact is availability loss through memory leakage, not code execution, data disclosure, or integrity compromise.
Researcher notes
The evidence supports a cleanup bug in a specific Linux DRM driver path. The source bundle does not provide proof-of-concept details, exploit maturity, or complete distribution version mapping. Validation should focus on kernel provenance, driver availability, and whether vendor backports include the stable cleanup commits.
Mitigation direction
- Apply vendor kernel updates containing the referenced stable fixes.
- Prioritize Linux systems where the Lima DRM driver is enabled or accessible.
- Check distribution advisories, including Debian LTS where applicable.
- Restrict untrusted local access to GPU/render devices where operationally feasible.
- Use vendor-supported kernels rather than unmanaged custom builds.
Validation and detection
- Inventory kernel versions and compare them with vendor fixed releases.
- Confirm whether the lima DRM module is built, loaded, or available.
- Review distribution security advisories for backported fixes.
- Check package changelogs for CVE-2024-35829 or referenced commits.
- Monitor affected systems for memory pressure or unexplained local availability failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-35829 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/f2e80ac9344aebbff576453d5c0290b332e187edCVE reference, Linux
- https://git.kernel.org/stable/c/746606d37d662c70ae1379fc658ee9c65f06880fCVE reference, Linux
- https://git.kernel.org/stable/c/f6d51a91b41704704e395de6839c667b0f810bbfCVE reference, Linux
- https://git.kernel.org/stable/c/8e25c0ee5665e8a768b8e21445db1f86e9156eb7CVE reference, Linux
- https://git.kernel.org/stable/c/4ab14eccf5578af1dd5668a5f2d771df27683cabCVE reference, Linux
- https://git.kernel.org/stable/c/ec6bb037e4a35fcbb5cd7bc78242d034ed893fcdCVE reference, Linux
- https://git.kernel.org/stable/c/04ae3eb470e52a3c41babe85ff8cee195e4dcbeaCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.htmlCVE reference, CVE · x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.