Kernel panic via uninitialized ALSA DMA mapping
Published Dec 27, 2024 · Updated May 11, 2026
NULL pointer dereference in ALSA PCM mmap handling in affected Linux kernels allows local users to trigger a kernel panic. The default snd_pcm_mmap_data_fault handler calls virt_to_page on runtime->dma_area without first ensuring that the pointer was initialized. Exploitation requires local PCM device access and a driver that permits mmap before initializing its DMA area; the demonstrated consequence is system interruption through a kernel panic.
Summary
What happened
NULL pointer dereference in ALSA PCM mmap handling in affected Linux kernels allows local users to trigger a kernel panic. The default snd_pcm_mmap_data_fault handler calls virt_to_page on runtime->dma_area without first ensuring that the pointer was initialized. Exploitation requires local PCM device access and a driver that permits mmap before initializing its DMA area; the demonstrated consequence is system interruption through a kernel panic.
The record
- CVE
- CVE-2024-53180
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 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.14
- Affected versionversion=d371588910715ebf7fa8e3a5d21ea5169c852927 <0c4c9bf5eab7bee6b606f2abb0993e933b5831a0
- Affected versionversion=d371588910715ebf7fa8e3a5d21ea5169c852927 <832efbb74b1578e3737d593a204d42af8bd1b81b
- Affected versionversion=d371588910715ebf7fa8e3a5d21ea5169c852927 <8799f4332a9fd812eadfbc32fc5104d6292f754f
- Affected versionversion=d371588910715ebf7fa8e3a5d21ea5169c852927 <bc200027ee92fba84f1826494735ed675f3aa911
- Affected versionversion=d371588910715ebf7fa8e3a5d21ea5169c852927 <d2913a07d9037fe7aed4b7e680684163eaed6bc4
- Affected versionversion=d371588910715ebf7fa8e3a5d21ea5169c852927 <f0ce9e24eff1678c16276f9717f26a78202506a2
What conditions does exploitation require?
What is affected?
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
- syzbot snd_pcm_mmap_data_fault reproducerproof of concept · demonstrated
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