CVE-2026-98116 — ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF snd_pcm_hw_params() and snd_pcm_hw_free() guard buffer reallocation with an mmap_count check performed under the PCM stream lock, but the lock is released long before the buffer is actually freed: snd_pcm_sync_stop(), constraint refinement and do_free_pages() all happen in between. snd_pcm_mmap_data(), on the other hand, takes no lock at all: it validates against the old buffer's state and dma_bytes, remaps its pages into the VMA, and only then increments mmap_count. A concurrent mmap() can therefore slip in between the check and the free. remap_pfn_range() installs writable PTEs for the old buffer's pages without taking page references, and the subsequent do_free_pages() returns those pages to the page allocator while the VMA still maps them. This leaves a stale, writable mapping of freed pages: a page-level use-after-free that can be leveraged for local privilege escalation. Make snd_pcm_mmap_data() participate in the buffer-access scheme introduced for hw_params/hw_free: acquire runtime->buffer_accessing before validating and remapping, and release it afterwards. Buffer reallocation already fails with -EBUSY while accessors are active, and the mmap side now fails with -EBUSY while a reallocation is in progress, so the validate/remap sequence and the check/free sequence can no longer interleave. A reproducer that turns this race into a stale writable mapping of the freed DMA buffer pages is available on request.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 0f6947f5f5208f6ebd4d76a82a4757e2839a23f8version 5.18≥ 5.17.1 and < 5.18≥ 5.16.18 and < 5.17≥ 5.10.109 and < 5.11≥ 5.4.193 and < 5.5≥ 4.19.243 and < 4.20≥ 4.14.279 and < 4.15 and 13 more≥ 5.15.32 and < 5.15.222version 1bbf82d9f961414d6c76a08f7f843ea068e0ab7bversion 0090c13cbbdffd7da079ac56f80373a9a1be0bf8≥ 33061d0fba51d2bf70a2ef9645f703c33fe8e438 and < e6cdd2a0470d64073349a970dc1691433804b271version fbeb492694ce0441053de57699e1e2b7bc148a69version 9cb6c40a6ebe4a0cfc9d6a181958211682cffea9version a42aa926843acca96c0dfbde2e835b8137f2f092≥ 92ee3c60ec9fe64404dc035e7c41277d74aa26cb and < 9b110a9dcecc59516c77cb3c0caf1f492f75df2d≥ 92ee3c60ec9fe64404dc035e7c41277d74aa26cb and < 8c1882dfee8f404d118020664b73eb4592172226≥ 92ee3c60ec9fe64404dc035e7c41277d74aa26cb and < fd137bf8149bc6460f9b7b1fc292025da04cb9ee≥ 92ee3c60ec9fe64404dc035e7c41277d74aa26cb and < cbc7ec97601d09b74e05e44470fa6b0bcdabf3f5≥ 92ee3c60ec9fe64404dc035e7c41277d74aa26cb and < cbadf2575d25e7dcc0d4da2717817ae569fbc99b≥ 92ee3c60ec9fe64404dc035e7c41277d74aa26cb and < 9857a75714bb5df4781e4d8b1a1753b1e17bf07a |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Undergoing Analysis
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- git.kernel.org/stable/c/9b110a9dcecc59516c77cb3c0caf1f492f75df2d
- git.kernel.org/stable/c/8c1882dfee8f404d118020664b73eb4592172226
- git.kernel.org/stable/c/fd137bf8149bc6460f9b7b1fc292025da04cb9ee
- git.kernel.org/stable/c/cbc7ec97601d09b74e05e44470fa6b0bcdabf3f5
- git.kernel.org/stable/c/e6cdd2a0470d64073349a970dc1691433804b271
- git.kernel.org/stable/c/cbadf2575d25e7dcc0d4da2717817ae569fbc99b
- git.kernel.org/stable/c/9857a75714bb5df4781e4d8b1a1753b1e17bf07a
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 22h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 22h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98116 is "ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.