CVE-2026-23191
What it is
In the Linux kernel, the following vulnerability has been resolved: ALSA: aloop: Fix racy access at PCM trigger The PCM trigger callback of aloop driver tries to check the PCM state and stop the stream of the tied substream in the corresponding cable. Since both check and stop operations are performed outside the cable lock, this may result in UAF when a program attempts to trigger frequently while opening/closing the tied stream, as spotted by fuzzers. For addressing the UAF, this patch changes two things: - It covers the most of code in loopback_check_format() with cable->lock spinlock, and add the proper NULL checks. This avoids already some racy accesses. - In addition, now we try to check the state of the capture PCM stream that may be stopped in this function, which was the major pain point leading to UAF.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 6.12.70
- Linux Kernel < 6.18.10
- Linux Kernel 6.19
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-23191.md and follow it. Check whether this project is affected by CVE-2026-23191. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/5727ccf9d19ca414cb76d9b647883822e2789c2e
- https://git.kernel.org/stable/c/826af7fa62e347464b1b4e0ba2fe19a92438084f
- https://git.kernel.org/stable/c/bad15420050db1803767e58756114800cce91ea4
References
- https://git.kernel.org/stable/c/0e6245b2424d126ac90018142d09f0707e12998b
- https://git.kernel.org/stable/c/5727ccf9d19ca414cb76d9b647883822e2789c2e
- https://git.kernel.org/stable/c/826af7fa62e347464b1b4e0ba2fe19a92438084f
- https://git.kernel.org/stable/c/bad15420050db1803767e58756114800cce91ea4
- https://git.kernel.org/stable/c/c99be0d5af02adebe9cb6f9869d20397fa9935a3
- https://git.kernel.org/stable/c/f3ce8be893726899e3053cf8059ecc95d8410359
- https://git.kernel.org/stable/c/f57467114f40c5aacebbea96fb4ff9e5cd2b7f18