Skip to main content

Linux Kernel CVE-2026-98116

| EUVDEUVD-2026-86947 HIGH
2026-09-25 Linux GHSA-pwf2-cf6j-p6wx
7.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local access to /dev/snd PCM device
  2. Delivery
    Spawn concurrent mmap() and hw_params/hw_free reallocation threads
  3. Exploit
    Win race so mmap maps buffer before do_free_pages frees it
  4. Execution
    Freed pages reallocated to other kernel objects
  5. Persist
    Write through stale writable mapping
  6. Impact
    Corrupt kernel memory for privilege escalation

Vulnerability Assessment

Exploitation Conditions

Requires local access to an ALSA PCM character device under /dev/snd (PR:L) and the ability to run concurrent threads issuing mmap() against a PCM stream while triggering buffer reallocation via SNDRV_PCM_IOCTL_HW_PARAMS/HW_FREE. Exploitation is a race condition: the attacker must win the window between snd_pcm_mmap_data() validating/remapping the old buffer and do_free_pages() freeing it - success is timing-dependent (limiting factor), though a reproducer reportedly makes it practical. No user interaction and no elevated privileges beyond audio-device access are needed; the flaw exists in default configurations on kernels compiled with ALSA PCM support (essentially all desktop/audio Linux builds). Not exploitable remotely.

Impact

This is one of the higher-priority Linux kernel flaws in the recent stable-tree batch because its impact is a genuine local privilege-escalation primitive rather than the crash-only DoS that is frequently mislabeled with C:H/I:H in this CVE family. The described mechanism - remap_pfn_range() installing WRITABLE PTEs for buffer pages that do_free_pages() then returns to the page allocator, leaving a stale writable mapping of freed pages that get reallocated to other kernel/user objects - cleanly supports the CVSS impact triad (C:H/I:H/A:H). The vendor CVSS is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8). I concur on impact and vector (AV:L, PR:L) but consider AC:L optimistic: exploitation is a TOCTOU race between a concurrent mmap() and the hw_params/hw_free reallocation path, which is inherently timing-dependent (AC:H is more honest, giving ~7.0), though the author notes a working reproducer exists which narrows that gap. No EPSS score, no CISA KEV entry, and no public exploit are present in the input - the reproducer is 'available on request', so it is NOT public. Net: a real, patch-worthy LPE candidate for prioritized kernel patching, but not evidence of in-the-wild exploitation. Signals are consistent (no CVSS-vs-description conflict); the main uncertainty is exploit reliability of the race, not the severity class.

Exploit ScenarioDerived

A local unprivileged (or low-privileged) user with access to a PCM device under /dev/snd opens two threads: one repeatedly calls mmap() on the PCM stream while the other drives snd_pcm_hw_params()/hw_free() to force buffer reallocation. By winning the race so the mmap validates and maps the old buffer just before do_free_pages() frees it, the attacker obtains a writable mapping of freed pages that the allocator later hands to other objects, then writes through it to corrupt kernel-owned data and escalate privileges. A private reproducer is stated to be available on request, but no public exploit code exists.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

A page-level use-after-free in the Linux kernel ALSA PCM subsystem lets a local user with access to a /dev/snd PCM character device turn a race between a concurrent mmap() and a buffer reallocation into a stale, writable mapping of freed DMA buffer pages, which can be reclaimed by the allocator and reused for local privilege escalation. The attacker must issue SNDRV_PCM_IOCTL_HW_PARAMS/HW_FREE from one thread while another thread mmaps the same PCM stream, and must win a narrow timing window (assessed CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H); no public exploit code has been identified at time of analysis, although the upstream commit states a reproducer is available on request, and this CVE is not in CISA KEV. Vendor patches are available in the stable trees (6.12.111, 6.18.53, 7.2.7) and mainline 7.3-rc2, with backports to older long-term branches, so unpatched kernels running ALSA PCM support remain exposed to any local user who can open a PCM device.

RemediationAI

Apply the vendor-released patch by upgrading to a fixed kernel: 6.12.111 or later on the 6.12 stable branch, 6.18.53 or later on the 6.18 branch, 7.2.7 or later on the 7.2 branch, or mainline 7.3-rc2 or later; distributions still carrying the older long-term branches should move to 4.14.279, 4.19.243, 5.4.193, 5.10.109, 5.15.32, 5.16.18 or 5.17.1 respectively, or simply take their vendor's kernel security update, since the fix is a small change that merely adds buffer_accessing acquisition/release around snd_pcm_mmap_data() and carries low regression risk outside concurrent mmap-during-reallocation workloads. There is no configuration-based fix for the race itself, so where patching cannot be scheduled immediately the practical compensating control is to remove untrusted local users' access to the ALSA PCM device nodes: tighten /dev/snd/* ownership and mode via udev rules, drop users from the audio group, and use SELinux or AppArmor policy to deny mmap() on PCM character devices to unprivileged domains. Stronger containment is to blacklist or not load the snd-pcm module (or build the kernel without CONFIG_SND_PCM) on servers, containers and multi-tenant hosts that do not need audio; the trade-off is complete loss of audio playback/capture, which breaks desktop sessions, VoIP, conferencing and any workload relying on ALSA (PulseAudio/PipeWire will fall back or fail). Note that these controls are partially effective only - device-node restrictions must cover every path to /dev/snd including nested containers and user namespaces - and none of them address the underlying freed-page reuse once an attacker legitimately holds a PCM descriptor.

Affected VersionsENISA

Linux 92ee3c60ec9fe64404dc035e7c41277d74aa26cb <9b110a9dcecc59516c77cb3c0caf1f492f75df2d
Linux patch: 7.3-rc2
Linux patch: 6.12.111
Linux 4.19.243 <4.20
Linux 5.15.32 <5.16
Linux 5.4.193 <5.5
Linux 4.14.279 <4.15
Linux fbeb492694ce0441053de57699e1e2b7bc148a69
Linux 5.10.109 <5.11
Linux 92ee3c60ec9fe64404dc035e7c41277d74aa26cb <8c1882dfee8f404d118020664b73eb4592172226
Linux 33061d0fba51d2bf70a2ef9645f703c33fe8e438
Linux patch: 6.18.53
Linux 92ee3c60ec9fe64404dc035e7c41277d74aa26cb <fd137bf8149bc6460f9b7b1fc292025da04cb9ee
Linux 5.17.1 <5.18
Linux 0f6947f5f5208f6ebd4d76a82a4757e2839a23f8
Linux patch: 7.2.7
Linux 9cb6c40a6ebe4a0cfc9d6a181958211682cffea9
Linux a42aa926843acca96c0dfbde2e835b8137f2f092
Linux 1bbf82d9f961414d6c76a08f7f843ea068e0ab7b
Linux 92ee3c60ec9fe64404dc035e7c41277d74aa26cb <cbc7ec97601d09b74e05e44470fa6b0bcdabf3f5
Linux 5.18
Linux 5.16.18 <5.17
Linux 0090c13cbbdffd7da079ac56f80373a9a1be0bf8
Linux patch: 0

Affected Packages

euvd linux fix: 4.15, 4.20, 5.5, 5.11, 5.16, 5.17, 5.18

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw lives in the ALSA PCM userspace interface, specifically snd_pcm_mmap_data() in the kernel sound subsystem. snd_pcm_hw_params() and snd_pcm_hw_free() guard DMA buffer reallocation with an mmap_count check taken under the PCM stream lock, but that lock is dropped well before the buffer is actually released: snd_pcm_sync_stop(), constraint refinement and do_free_pages() all execute in the interval. snd_pcm_mmap_data() took no lock at all - it validated against the old buffer's state and dma_bytes, called remap_pfn_range() to install writable PTEs for the old buffer's pages (without taking page references), and only afterwards incremented mmap_count. A concurrent mmap() could therefore interleave between the check and the free, so do_free_pages() returned pages to the page allocator while a user VMA still mapped them writable. This is a classic time-of-check-to-time-of-use race (CWE-362 class) terminating in use-after-free of physical pages (CWE-416 class); no CWE identifier was assigned in the CVE record. The fix makes snd_pcm_mmap_data() participate in the runtime->buffer_accessing scheme introduced for hw_params/hw_free: it acquires buffer_accessing before validating and remapping and releases it afterwards, so reallocation now fails with -EBUSY while an mmap accessor is active and the mmap path fails with -EBUSY while reallocation is in progress, making the validate/remap and check/free sequences mutually exclusive. Because this is core PCM machinery, any kernel built with ALSA PCM support (CONFIG_SND_PCM, i.e. essentially every general-purpose desktop, workstation and audio-enabled server kernel) is in scope; the CPE data (cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*) is version-agnostic and therefore the kernel version ranges below are the authoritative scoping signal.

Know when Alsa gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local /dev/snd access gives AV:L/PR:L; the check-vs-free TOCTOU race is timing-dependent so AC:H (vs vendor AC:L); stale writable mapping of reallocated freed pages justifies C:H/I:H/A:H.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat 7.8 HIGH

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Sep 25, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Sep 25, 2026 - 12:02 EUVD
CVE Published
Sep 25, 2026 - 10:36 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 25, 2026 - 10:36 cve.org
HIGH 7.8

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Unpatched Linux kernels carry a local privilege-escalation flaw in the ALSA PCM audio subsystem (CVE-2026-98116) that affects any host where a non-privileged user, service account, or container can open an audio device node. A successful attacker gains root-level control of the machine, turning routine audio access into full system compromise, so leadership should care most about multi-tenant servers, container platforms, developer workstations, and any fleet running unpatched kernels. No public exploit code has been identified at time of analysis and the race window is narrow, but the potential for complete host takeover keeps this a high-priority remediation item.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
High
ALSA PCM is core Linux audio, present on nearly all desktop/audio Linux installs
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy