Service interruption via leaked DMA framebuffer memory
Published May 6, 2026 · Updated May 6, 2026
Resource leak in the Linux Kernel vt8500lcdfb driver allows local users to exhaust DMA-coherent memory through a failed device probe. vt8500lcd_probe allocates fbi->fb.screen_buffer with dma_alloc_coherent(), then its palette-allocation failure branch skips the matching dma_free_coherent() cleanup. Repeatedly reaching this hardware-specific error path consumes kernel DMA memory and can interrupt service; no data disclosure or modification is reported.
Summary
What happened
Resource leak in the Linux Kernel vt8500lcdfb driver allows local users to exhaust DMA-coherent memory through a failed device probe. vt8500lcd_probe allocates fbi->fb.screen_buffer with dma_alloc_coherent(), then its palette-allocation failure branch skips the matching dma_free_coherent() cleanup. Repeatedly reaching this hardware-specific error path consumes kernel DMA memory and can interrupt service; no data disclosure or modification is reported.
The record
- CVE
- CVE-2026-43202
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- 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=3.7
- Affected versionversion=e7b995371fe1e29838321fcdc3cfe35bb0d6bfc4 <2cd2f988a8bd2da227f5c3cfa0cbf3a9a287ddc3
- Affected versionversion=e7b995371fe1e29838321fcdc3cfe35bb0d6bfc4 <40c1ff25025150ff6d7ec7ad441fcfd6d070ee76
- Affected versionversion=e7b995371fe1e29838321fcdc3cfe35bb0d6bfc4 <778f31be5b8c10024db23fdd8a05f68a02311008
- Affected versionversion=e7b995371fe1e29838321fcdc3cfe35bb0d6bfc4 <88b3b9924337336a31cefbe99a22ed09401be74a
- Affected versionversion=e7b995371fe1e29838321fcdc3cfe35bb0d6bfc4 <9a9bc60ed372aaae9784ff8ad8e5f496ff15fd31
- Affected versionversion=e7b995371fe1e29838321fcdc3cfe35bb0d6bfc4 <9c3873cccb3fab54cde0605ae7093d332c99073e
- Affected versionversion=e7b995371fe1e29838321fcdc3cfe35bb0d6bfc4 <e8c5d5f6cd66e032f9aefdcc21b0c34761aef78a
- Affected versionversion=e7b995371fe1e29838321fcdc3cfe35bb0d6bfc4 <f47d5b9e8aa6178a0aaf225119ad1ec7d3f49876
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