CVE-2023-54254

What it actually does

On eviction errors other than -EMULTIHOP the TTM resource is not released, causing a memory leak in the Linux kernel DRM subsystem.

Why it matters to the business

Repeated triggering of the error path can exhaust kernel memory, leading to degraded graphics performance, system instability, or crashes on affected Linux systems.

How an attack unfolds

An attacker with local access triggers DRM eviction operations that return errors other than -EMULTIHOP, causing the kernel to leak resources with each failure until memory pressure impacts system operation.

How to fix it

Update the Linux kernel to a version containing commit 7738335d73d0686ec8995e0448e5d1b48cffb2a4 or later stable releases that include the fix.

How to confirm the fix worked

Confirm the running kernel contains commit 7738335d73d0686ec8995e0448e5d1b48cffb2a4 and test eviction error paths to verify resources are released.

Typical attack path

1. Obtain local code execution on a Linux system with DRM/TTM in use
2. Craft or trigger graphics operations that induce TTM eviction failures
3. Repeat the error-inducing sequence to accumulate leaked resources
4. Monitor for memory exhaustion or system instability

How to detect it

Review kernel logs for repeated TTM eviction error paths and monitor memory usage trends on systems running vulnerable kernels; no public exploit artifacts are known.

What your security team should do

• Prioritize kernel updates on all Linux systems exposing graphics workloads
• Monitor EPSS and exploit maturity signals for any rise in activity
• Apply the fix in the next maintenance window given the low but non-zero EPSS