Local kernel crash via unchecked DMA allocation
Published Jul 24, 2026 · Updated Jul 24, 2026
NULL pointer dereference in the Linux Kernel pch_uart driver allows local users to crash the kernel during receive DMA setup. The driver fails to check whether dma_alloc_coherent() returned NULL before dma_handle_rx() uses the receive buffer. Reachability requires local access, the EG20T PCH UART driver on compatible hardware, and a failed DMA allocation; only a kernel crash is documented.
Summary
What happened
NULL pointer dereference in the Linux Kernel pch_uart driver allows local users to crash the kernel during receive DMA setup. The driver fails to check whether dma_alloc_coherent() returned NULL before dma_handle_rx() uses the receive buffer. Reachability requires local access, the EG20T PCH UART driver on compatible hardware, and a failed DMA allocation; only a kernel crash is documented.
The record
- CVE
- CVE-2026-64234
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 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=2.6.38
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <5f2e2a240dc1846e049bc67e9c3cdf5b031d08bf
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <66f8bfea055b23719b4fd6ce207c44de37d82a59
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <6dd5c0ea139b586ad5a091677056dafd405cfe82
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <6fe472c1bbbe238e91141f7cabc1226e96a60d43
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <760df81763b391bb5f0dcb0b7597b736da753ae4
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <d846df2dfbc2469a688833b4cc4f8aa80672bde8
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <d8d53a343ebe74274ca17b1e1993042e99f8c863
- Affected versionversion=3c6a483275f47a2ef7119309ad3d791c10cf30da <daea997bb244aeb50cbb2e5e075fb446a6cf068f
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.
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