ASoC: cs35l33: drain threaded IRQ before runtime suspend
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e074c12c428c633e079154301207a6079a208583, Kernel 5b5311427e54d9c0d07178ee42df68ba44c2d5ca, Kernel 614c2616ea677abfbed917a92bdc5141efff3536 and 12 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <e074c12c428c633e079154301207a6079a208583, >=3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <5b5311427e54d9c0d07178ee42df68ba44c2d5ca, >=3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <614c2616ea677abfbed917a92bdc5141efff3536, >=3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <6ae98918240585eb2ad32b097c4810f4e2dabe88, >=3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2, >=3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <84cf6acd01a1ec8f30276578a039216327af782e, >=3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <a04722542c76ce861031384480825afded8cc4f4, >=3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 <d07799302721d381aef834fac8a11d196894eccb, =4.8 | e074c12c428c633e079154301207a6079a208583, 5b5311427e54d9c0d07178ee42df68ba44c2d5ca, 614c2616ea677abfbed917a92bdc5141efff3536, 6ae98918240585eb2ad32b097c4810f4e2dabe88, 6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2, 84cf6acd01a1ec8f30276578a039216327af782e, a04722542c76ce861031384480825afded8cc4f4, d07799302721d381aef834fac8a11d196894eccb |
| linux-kernel: Kernel | >=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.51, >=6.19.0 <7.2.5, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=4.8.0 <5.10.270 | 5.15.221, 6.1.188, 6.18.51, 7.2.5, 6.6.157, 6.12.110, 5.10.270 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket