CVEvulnerability
CVE-2026-23191
7.0 HIGH
Official page ↗
- Status
- Modified
- Published
- 2026-02-14
- Last modified
- 2026-10-19
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 7.0 HIGH — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-362, CWE-416
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.
Affected configurations
• linux linux kernel (>= 2.6.37 < 6.12.70)
• linux linux kernel (>= 6.13 < 6.18.10)
• linux linux kernel 6.19
Related
References
- https://git.kernel.org/stable/c/0e6245b2424d126ac90018142d09f0707e12998b git.kernel.org
- https://git.kernel.org/stable/c/5727ccf9d19ca414cb76d9b647883822e2789c2e Patch
- https://git.kernel.org/stable/c/826af7fa62e347464b1b4e0ba2fe19a92438084f Patch
- https://git.kernel.org/stable/c/bad15420050db1803767e58756114800cce91ea4 Patch
- https://git.kernel.org/stable/c/c99be0d5af02adebe9cb6f9869d20397fa9935a3 git.kernel.org
- https://git.kernel.org/stable/c/f3ce8be893726899e3053cf8059ecc95d8410359 git.kernel.org
- https://git.kernel.org/stable/c/f57467114f40c5aacebbea96fb4ff9e5cd2b7f18 git.kernel.org