CVE-2026-43269
Memory Leak in Linux Kernel DRM/Atmel-HLCDC Driver
Publication date: 2026-05-06
Last updated on: 2026-05-06
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/atmel-hlcdc component. Specifically, some drm_crtc_commit objects are not properly freed because the atomic_destroy_state callback only releases the framebuffer, but does not release all associated objects. The fix involves using the __drm_atomic_helper_plane_destroy_state() function to ensure all unneeded objects are freed.
The issue causes slab memory to increase over time, which can be observed after hours of running a graphics application or by using the kmemleak tool.
How can this vulnerability impact me? :
This vulnerability can lead to a memory leak in the Linux kernel when using certain graphics applications. Over time, the system's memory consumption may increase due to unreleased drm_crtc_commit objects, potentially degrading system performance or causing resource exhaustion.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for memory leaks related to drm_crtc_commit objects in the Linux kernel, especially after prolonged use of graphics applications.
Using the kmemleak tool is suggested to identify unreferenced objects that indicate memory leaks.
An example output from kmemleak includes unreferenced objects with details such as command name, process ID, and backtrace information.
To detect this issue, you can enable and use kmemleak with commands like:
- echo scan > /sys/kernel/debug/kmemleak
- cat /sys/kernel/debug/kmemleak
These commands trigger a scan for memory leaks and display any unreferenced objects found.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by fixing the memory leak in the drm/atmel-hlcdc driver by using the __drm_atomic_helper_plane_destroy_state() function to properly free all objects.
Immediate mitigation involves updating the Linux kernel to a version that includes this fix.
Until the update is applied, monitoring for memory leaks using kmemleak and limiting prolonged use of affected graphics applications may help reduce impact.