CVE-2026-46090: ALSA: aloop: Fix peer runtime UAF during format-change stop
In the Linux kernel, the following vulnerability has been resolved:
ALSA: aloop: Fix peer runtime UAF during format-change stop
loopback_check_format() may stop the capture side when playback starts
with parameters that no longer match a running capture stream. Commit
826af7fa62e3 ("ALSA: aloop: Fix racy access at PCM trigger") moved
the peer lookup under cable->lock, but the actual snd_pcm_stop() still
runs after dropping that lock.
A concurrent close can clear the capture entry from cable->streams[] and
detach or free its runtime while the playback trigger path still holds a
stale peer substream pointer.
Keep a per-cable count of in-flight peer stops before dropping
cable->lock, and make free_cable() wait for those stops before
detaching the runtime. This preserves the existing behavior while
making the peer runtime lifetime explicit.
Security readout for executives and security teams
Plain-English summary
CVE-2026-46090 is a Linux kernel flaw in the ALSA loopback audio driver. A local user could potentially trigger a race that uses freed memory, with high impact to confidentiality, integrity, and availability. It is not described as remotely exploitable in the provided sources.
Executive priority
Treat this as a high-priority kernel maintenance item, especially on shared Linux systems. It is less urgent than a remotely exploitable internet-facing flaw, but local privilege impact can be severe in multi-user environments.
Technical view
The issue is a use-after-free race in ALSA aloop during format-change stop handling. A concurrent close can detach or free a capture runtime while playback trigger logic still holds a stale peer substream pointer. Stable fixes add in-flight peer stop tracking and wait before runtime detach.
Likely exposure
Exposure is most relevant to affected Linux kernel builds where the ALSA loopback driver is present and local users can interact with audio devices. Shared Linux servers, desktops, build hosts, and container hosts with untrusted local access deserve review.
Exploitation context
The CVSS vector is local, low complexity, low privileges, and no user interaction. The source bundle says KEV is false and provides no cited evidence of active exploitation or public weaponization.
Researcher notes
Evidence supports a race-related use-after-free in snd-aloop peer runtime lifetime handling. The bundle includes stable kernel commits and Red Hat advisories, but does not provide exploit details, affected distribution package matrices, or proof of active exploitation.
Mitigation direction
Apply vendor kernel updates that include the referenced stable fixes.
Review Red Hat advisories for affected package status and update guidance.
Prioritize systems with untrusted local users or shared shell access.
If patching is delayed, follow vendor guidance for temporary controls.
Reboot into the updated kernel after maintenance completes.
Validation and detection
Inventory running Linux kernel versions across managed systems.
Check whether vendor advisories mark each platform affected or fixed.
Confirm the updated kernel includes the referenced stable commit lineage.
Review whether ALSA loopback support is present on exposed systems.
Document systems requiring reboot to activate the fixed kernel.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-364: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
1ADP providers
23Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-364 · source CWE mapping
Signal Handler Race Condition
Signal Handler Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.