CVE-2026-89946

ASoC: cs35l33: drain threaded IRQ before runtime suspend

N/A
Published: September 16, 2026 at 10:32 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3333cb7187b9c8d28f7a6405bbe9cec7a10efdc84.8
Vendor states this is fixed in 5b5311427e54d9c0d07178ee42df68ba44c2d5ca (fixed)
Vendor states this is fixed in 614c2616ea677abfbed917a92bdc5141efff3536 (fixed)
Vendor states this is fixed in 6ae98918240585eb2ad32b097c4810f4e2dabe88 (fixed)
Vendor states this is fixed in 6e369bc46663b4bfce3d5f8b8ed08e71ecea13a2 (fixed)
Vendor states this is fixed in 84cf6acd01a1ec8f30276578a039216327af782e (fixed)
Vendor states this is fixed in a04722542c76ce861031384480825afded8cc4f4 (fixed)
Vendor states this is fixed in d07799302721d381aef834fac8a11d196894eccb (fixed)
Vendor states this is fixed in e074c12c428c633e079154301207a6079a208583 (fixed)
Vendor states this is fixed in 4.8 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card