Service interruption via leaked DRM display modes
Published Dec 24, 2025 · Updated Dec 24, 2025
Memory leak in Linux kernel 2.6.35 through 6.4.7 allows local users to interrupt service through repeated DRM fbdev setup. The drm_client_target_cloned function duplicates a display mode into dmt_mode but returns without freeing that allocation, leaving 128-byte objects orphaned. Triggering the path requires local low-privileged access and a DRM driver using generic fbdev setup; the ast driver demonstrated the leak.
Summary
What happened
Memory leak in Linux kernel 2.6.35 through 6.4.7 allows local users to interrupt service through repeated DRM fbdev setup. The drm_client_target_cloned function duplicates a display mode into dmt_mode but returns without freeing that allocation, leaving 128-byte objects orphaned. Triggering the path requires local low-privileged access and a DRM driver using generic fbdev setup; the ast driver demonstrated the leak.
The record
- CVE
- CVE-2023-54091
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record 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=1d42bbc8f7f9ce4d852692ef7aa336b133b0830a <105275879a80503686a8108af2f5c579a1c5aef4
- Affected versionversion=1d42bbc8f7f9ce4d852692ef7aa336b133b0830a <4b596a6e2d2e0f9c14e4122506dd715f43fcd727
- Affected versionversion=1d42bbc8f7f9ce4d852692ef7aa336b133b0830a <52daf6ba2e0d201640cb1ce42049c5c4426b4d6e
- Affected versionversion=1d42bbc8f7f9ce4d852692ef7aa336b133b0830a <a4b978249e8fa94956fce8b70a709f7797716f62
- Affected versionversion=1d42bbc8f7f9ce4d852692ef7aa336b133b0830a <a85e23a1ef63e45a18f0a30d7816fcb4a865ca95
- Affected versionversion=1d42bbc8f7f9ce4d852692ef7aa336b133b0830a <b5359d7a5087ac398fc429da6833133b4784c268
- Affected versionversion=1d42bbc8f7f9ce4d852692ef7aa336b133b0830a <c2a88e8bdf5f6239948d75283d0ae7e0c7945b03
- Affected versionversion=1d42bbc8f7f9ce4d852692ef7aa336b133b0830a <d3009700f48602b557eade1f22c98b6bc20247e8
- Affected versionversion=2.6.35
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
No sourced classifications are available.
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