ASoC: cs35l34: drain threaded IRQ before runtime suspend
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux 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 Linux
4.10
- KernelLinux
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
References 8
git.kernel.org
- stable/c/3be8380fb14d602cd833e5852e6d83c1e7eb1ceb
- stable/c/96982734e765c13c3db02067e1d5784682085f5c
- stable/c/5b063739619990d5de0c94c85d6e5be14e7cbdfe
- stable/c/f4bfd755c52dfa7584e6c9374206b71b8895c997
- stable/c/4fe8a91a9266f1321c2d31ce67940a4e8b93559e
- stable/c/5a4fe7a87841af23ba80bae31b80355b16926cf4
- stable/c/07a86575edc308e66b6c8873ed4a93ef3a063e55
- stable/c/4105a4c0678b2808fc8046b60321b4f1cc7dae75