Service interruption via unreleased DRM commit objects
Published May 6, 2026 · Updated May 6, 2026
A memory leak in the Atmel HLCDC DRM driver in Linux Kernel allows local users to exhaust kernel memory through repeated display commits. The atmel_hlcdc_plane_atomic_destroy_state callback releases only the framebuffer instead of all plane-state objects, leaving drm_crtc_commit allocations referenced. Reaching the flaw requires local low-privilege access to issue repeated DRM modeset ioctls on a system using the Atmel HLCDC driver; sustained activity can exhaust slab memory and interrupt service.
Summary
What happened
A memory leak in the Atmel HLCDC DRM driver in Linux Kernel allows local users to exhaust kernel memory through repeated display commits. The atmel_hlcdc_plane_atomic_destroy_state callback releases only the framebuffer instead of all plane-state objects, leaving drm_crtc_commit allocations referenced. Reaching the flaw requires local low-privilege access to issue repeated DRM modeset ioctls on a system using the Atmel HLCDC driver; sustained activity can exhaust slab memory and interrupt service.
The record
- CVE
- CVE-2026-43269
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <082271e364a3205598c2e4e6233a9f49ce7941cf
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <25e832a7830740e72103eb0b527680a4b64bbcb3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e64e78f4a70e3f6ac8fe5a7071f08ffd25a2489
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5718d98976ad6b9700e5a6afec67fc47a8a92580
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <57fa3487acfa3467405f8506b94682abd96e7393
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d4e91ab97fda64e8cf9c8881cc3b4da026bd849
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ec40702029b08ee8d5f5b03303d64a10e74a957b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f12352471061df83a36edf54bbb16284793284e4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo