CVE-2026-23191 is a time-of-check/time-of-use race condition in the Linux kernel ALSA aloop loopback driver. The PCM trigger callback checks PCM state and stops a tied substream without holding the corresponding cable lock. Frequent PCM triggering concurrent with opening or closing the tied stream can cause use-after-free. The affected logic includes loopback_check_format(), particularly its handling of the capture PCM stream that may be stopped. Exploitation may cause kernel instability, crashes, or memory corruption.
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.
53 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A race-condition vulnerability in the Linux kernel ALSA loopback (aloop) PCM trigger path.
A Unity Linux vulnerability tracked as CVE-2026-23191. Exploitation requires local access, high attack complexity, and low privileges, but could result in high confidentiality, integrity, and availability impact.
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.
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.