ASoC: cs35l33: 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: cs35l33: drain threaded IRQ before runtime suspend cs35l33_runtime_suspend() currently switches the codec into regcache_cache_only(true) and powers it down without first quiescing the threaded IRQ registered by devm_request_threaded_irq(). That leaves a window where cs35l33_irq_thread() can still run after suspend has closed off live register 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/2 after cache_only has been enabled, ignores the regmap_read() failures, and can still drive the AMP_SHORT_RLS, CAL_ERR_RLS, OTE_RLS, and OTW_RLS release paths. Use disable_irq() before entering cache_only/power-off so any in-flight threaded handler is drained and no new IRQ thread can run during the suspended state. Re-enable the IRQ only after runtime_resume() has restored live register access with regcache_sync(). Since probe only warns if devm_request_threaded_irq() fails, track whether the IRQ was actually installed before disabling or re-enabling it.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · fixed in d07799302721d381aef834fac8a11d196894eccb; From 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · fixed in 5b5311427e54d9c0d07178ee42df68ba44c2d5ca; From 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · fixed in a04722542c76ce861031384480825afded8cc4f4; From 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · fixed in 614c2616ea677abfbed917a92bdc5141efff3536; From 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · fixed in 6ae98918240585eb2ad32b097c4810f4e2dabe88; From 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · fixed in 6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2; From 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · fixed in 84cf6acd01a1ec8f30276578a039216327af782e; From 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · fixed in e074c12c428c633e079154301207a6079a208583
- Linux Linux
4.8
- KernelLinux
From 4.8.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/d07799302721d381aef834fac8a11d196894eccb
- stable/c/5b5311427e54d9c0d07178ee42df68ba44c2d5ca
- stable/c/a04722542c76ce861031384480825afded8cc4f4
- stable/c/614c2616ea677abfbed917a92bdc5141efff3536
- stable/c/6ae98918240585eb2ad32b097c4810f4e2dabe88
- stable/c/6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2
- stable/c/84cf6acd01a1ec8f30276578a039216327af782e
- stable/c/e074c12c428c633e079154301207a6079a208583