CVE-2026-89945

ASoC: cs35l34: 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: 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.

Affected

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

4.10c1124c09e1035cabdbc17d4538ae6f922086fec9
Vendor states this is fixed in 07a86575edc308e66b6c8873ed4a93ef3a063e55 (fixed)
Vendor states this is fixed in 3be8380fb14d602cd833e5852e6d83c1e7eb1ceb (fixed)
Vendor states this is fixed in 4105a4c0678b2808fc8046b60321b4f1cc7dae75 (fixed)
Vendor states this is fixed in 4fe8a91a9266f1321c2d31ce67940a4e8b93559e (fixed)
Vendor states this is fixed in 5a4fe7a87841af23ba80bae31b80355b16926cf4 (fixed)
Vendor states this is fixed in 5b063739619990d5de0c94c85d6e5be14e7cbdfe (fixed)
Vendor states this is fixed in 96982734e765c13c3db02067e1d5784682085f5c (fixed)
Vendor states this is fixed in f4bfd755c52dfa7584e6c9374206b71b8895c997 (fixed)
Vendor states this is fixed in 4.10 (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