CVE-2023-54091
Memory Leak in Linux Kernel DRM Client Affects Multiple Drivers
Publication date: 2025-12-24
Last updated on: 2025-12-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's DRM (Direct Rendering Manager) client code, specifically in the function drm_client_target_cloned. The issue occurs because the dmt_mode object is allocated but never freed, leading to a leak of kernel memory. It was initially found with the ast driver, but it likely affects most drivers using the generic fbdev setup.
How can this vulnerability impact me? :
The memory leak can cause increased memory usage in the kernel over time, potentially leading to degraded system performance or instability. If the leak is severe or exploited in a specific context, it could contribute to denial of service by exhausting kernel memory resources.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is a memory leak in the Linux kernel's drm client code, specifically in drm_client_target_cloned. It was identified through a kmemleak report. To detect this vulnerability on your system, you can use the Linux kernel's kmemleak tool to scan for memory leaks. Enable kmemleak by booting the kernel with the parameter 'kmemleak=on' and then check for reports using the command: 'cat /sys/kernel/debug/kmemleak'. This will show unreferenced objects that may indicate leaks such as the one described.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this memory leak in drm_client_target_cloned has been fixed. Since the issue is a memory leak in the drm client code affecting drivers using generic fbdev setup, applying the patch or upgrading to the fixed kernel version will resolve the problem. In the meantime, monitoring system memory usage and restarting affected services or the system may help reduce impact.