CVE-2026-23191ALSA: aloop: Fix racy access at PCM trigger
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 32 days later
· 32 days later
Published
- 8 months later
· 8 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 97% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected b1c73fc8e697eb73e23603e465e9af2711ed4183 – < f57467114f40c5aacebbea96fb4ff9e5cd2b7f18
- affected b1c73fc8e697eb73e23603e465e9af2711ed4183 – < c99be0d5af02adebe9cb6f9869d20397fa9935a3
- affected b1c73fc8e697eb73e23603e465e9af2711ed4183 – < f3ce8be893726899e3053cf8059ecc95d8410359
- affected b1c73fc8e697eb73e23603e465e9af2711ed4183 – < 0e6245b2424d126ac90018142d09f0707e12998b
- affected b1c73fc8e697eb73e23603e465e9af2711ed4183 – < bad15420050db1803767e58756114800cce91ea4
- affected b1c73fc8e697eb73e23603e465e9af2711ed4183 – < 5727ccf9d19ca414cb76d9b647883822e2789c2e
- affected b1c73fc8e697eb73e23603e465e9af2711ed4183 – < 826af7fa62e347464b1b4e0ba2fe19a92438084f
- affected 2.6.37
- unaffected < 2.6.37
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.70 – ≤ 6.12.*
- unaffected 6.18.10 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References7
- https://git.kernel.org/stable/c/f57467114f40c5aacebbea96fb4ff9e5cd2b7f18 (opens in a new tab)
- https://git.kernel.org/stable/c/c99be0d5af02adebe9cb6f9869d20397fa9935a3 (opens in a new tab)
- https://git.kernel.org/stable/c/f3ce8be893726899e3053cf8059ecc95d8410359 (opens in a new tab)
- https://git.kernel.org/stable/c/0e6245b2424d126ac90018142d09f0707e12998b (opens in a new tab)
- https://git.kernel.org/stable/c/bad15420050db1803767e58756114800cce91ea4 (opens in a new tab)
- https://git.kernel.org/stable/c/5727ccf9d19ca414cb76d9b647883822e2789c2e (opens in a new tab)
- https://git.kernel.org/stable/c/826af7fa62e347464b1b4e0ba2fe19a92438084f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-6109 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-23191)Record last updated .