Kernel crash via unconditional DMA channel unregistration
Published Feb 29, 2024 · Updated May 11, 2026
NULL pointer dereference in Linux kernel dmaengine allows local users with high privileges to crash the kernel during channel cleanup. After channel registration fails and frees chan->local, __dma_async_device_channel_unregister() unconditionally unregisters the channel and dereferences the null pointer. Reaching the fault requires privileged local control of a DMA controller driver or the managed unregistration path, and the bounded consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in Linux kernel dmaengine allows local users with high privileges to crash the kernel during channel cleanup. After channel registration fails and frees chan->local, __dma_async_device_channel_unregister() unconditionally unregisters the channel and dereferences the null pointer. Reaching the fault requires privileged local control of a DMA controller driver or the managed unregistration path, and the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2023-52492
- Published
- Feb 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.6
- Affected versionversion=d2fb0a0438384fee08a418025f743913020033ce <047fce470412ab64cb7345f9ff5d06919078ad79
- Affected versionversion=d2fb0a0438384fee08a418025f743913020033ce <2ab32986a0b9e329eb7f8f04dd57cc127f797c08
- Affected versionversion=d2fb0a0438384fee08a418025f743913020033ce <7f0ccfad2031eddcc510caf4e57f2d4aa2d8a50b
- Affected versionversion=d2fb0a0438384fee08a418025f743913020033ce <9263fd2a63487c6d04cbb7b74a48fb12e1e352d0
- Affected versionversion=d2fb0a0438384fee08a418025f743913020033ce <9de69732dde4e443c1c7f89acbbed2c45a6a8e17
- Affected versionversion=d2fb0a0438384fee08a418025f743913020033ce <f5c24d94512f1b288262beda4d3dcb9629222fc7
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