CVE-2026-23191 is a race-condition vulnerability in the Linux kernel ALSA aloop loopback driver. The flaw is in PCM trigger handling, where the driver checks PCM state and stops the tied substream in the corresponding cable outside the protection of the cable lock. This unsynchronized access allows concurrent trigger activity and open/close operations on the paired stream to invalidate objects while they are still being referenced, resulting in a use-after-free condition. The issue was observed under frequent trigger operations combined with opening and closing the tied stream. The upstream fix expands coverage of the cable spinlock around most of loopback_check_format(), adds NULL checks, and changes the logic to verify the state of the capture PCM stream before attempting to stop it.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
49 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel ALSA aloop race condition vulnerability at PCM trigger, fixed in this Red Hat kernel update.
A Linux kernel ALSA aloop race condition vulnerability at PCM trigger.
A Linux kernel ALSA aloop flaw involving racy access at PCM trigger.
A Linux kernel ALSA aloop vulnerability caused by racy access at PCM trigger.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.