Kernel memory corruption via unlocked PCM preallocation writes
Published Feb 26, 2025 · Updated May 11, 2026
Use-after-free in ALSA PCM preallocation in Linux allows local users with proc-write access to corrupt kernel memory through concurrent writes. The snd_pcm_lib_preallocate_proc_write function changes DMA-buffer allocation without taking open_mutex, allowing it to race with PCM stream opens and later operations. The proc entry is root-owned and mode 0644, so exploitation requires UID 0 or CAP_DAC_OVERRIDE; the published impact is memory corruption, not a demonstrated privilege gain.
Summary
What happened
Use-after-free in ALSA PCM preallocation in Linux allows local users with proc-write access to corrupt kernel memory through concurrent writes. The snd_pcm_lib_preallocate_proc_write function changes DMA-buffer allocation without taking open_mutex, allowing it to race with PCM stream opens and later operations. The proc entry is root-owned and mode 0644, so exploitation requires UID 0 or CAP_DAC_OVERRIDE; the published impact is memory corruption, not a demonstrated privilege gain.
The record
- CVE
- CVE-2022-49288
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 26, 2025CVE 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <37b12c16beb6f6c1c3c678c1aacbc46525c250f7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <51fce708ab8986a9879ee5da946a2cc120f1036d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <69534c48ba8ce552ce383b3dfdb271ffe51820c3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a21d2f323b5a978dedf9ff1d50f101f85e39b3f2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b560d670c87d7d40b3cf6949246fa4c7aa65a00a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e14dca613e0a6ddc2bf6e360f16936a9f865205b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e7786c445bb67a9a6e64f66ebd6b7215b153ff7d
- Affected versionversion=2.6.12
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