CVE-2023-54254: drm/ttm: Don't leak a resource on eviction error
In the Linux kernel, the following vulnerability has been resolved:
drm/ttm: Don't leak a resource on eviction error
On eviction errors other than -EMULTIHOP we were leaking a resource.
Fix.
v2:
- Avoid yet another goto (Andi Shyti)
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a resource leak in the DRM TTM graphics memory manager when certain eviction errors occur. The source does not provide CVSS, CWE, or a concrete business impact. Treat it as a kernel maintenance risk until your Linux vendor maps it to supported packages and fixed kernel builds.
Executive priority
Handle through normal kernel patch governance unless vendor guidance raises severity. It deserves tracking because kernel resource leaks can affect availability, but the provided sources do not support emergency response, confirmed exploitation, or a defined privilege-escalation scenario.
Technical view
The resolved bug is in drm/ttm eviction handling. For eviction errors other than -EMULTIHOP, a resource was leaked. Stable kernel commits are referenced as fixes. The bundle does not describe an attack path, required privileges, reachable device paths, or whether repeated triggering can cause denial of service.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions or downstream kernels containing the vulnerable DRM/TTM code. Systems using graphics drivers or workloads that exercise TTM eviction paths may be more relevant. Confirm exposure through your distribution kernel advisory because the bundle provides upstream versions and commits, not distro package mappings.
Exploitation context
There is no KEV listing and no cited source in the bundle showing active exploitation or public exploit availability. The public description only states a resource leak on an eviction error path. Any exploitability assessment beyond resource-leak behavior would be speculative from the provided evidence.
Researcher notes
Key gaps: no CVSS, CWE, reproducer, threat model, privilege requirement, or downstream package mapping. Research should focus on reachability of the eviction error path, whether leaks are attacker-repeatable, and which GPU drivers or workloads can trigger non--EMULTIHOP failures.
Mitigation direction
Identify Linux kernels matching the affected upstream versions in the bundle.
Check your distribution or appliance vendor advisory for fixed kernel packages.
Upgrade to a kernel containing the referenced stable fixes when available.
Prioritize systems with graphics, GPU, or DRM/TTM-dependent workloads.
Track vendor severity if CVSS or operational impact is later published.
Validation and detection
Inventory kernel versions across Linux servers, desktops, and appliances.
Map running kernels to vendor advisories and upstream stable fix commits.
Review change logs for the drm/ttm eviction resource-leak fix.
Confirm patched systems boot the intended fixed kernel.
Monitor kernel logs for recurring DRM or TTM eviction errors.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
cve · low confidence lookup
CVE-2023-54254 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
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.
Dec 30, 2025, 12:15 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.