ASoC: cs35l33: drain threaded IRQ before runtime suspend
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3333cb7187b9c8d28f7a6405bbe9cec7a10efdc8 · < 6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The cs35l33 driver can power down the codec while its threaded fault IRQ handler is still running. If a fault IRQ overlaps runtime suspend, the handler can read registers after live access is disabled and continue into fault-release paths despite read failures. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux systems that use the cs35l33 driver should check their kernel version; affected versions are not specified.