CVE-2026-89945

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

sound/soc/codecs/cs35l34.c

What this is

CIRRUS LOGIC AUDIO CODEC DRIVERSMAINTAINERS section matched on sound/soc/codecs/cs* · linux-sound@vger.kernel.org · Maintained

Kernel module

none to look for. The file would have gone into snd_soc_cs35l34, and Debian does not compile it into that module, so finding snd_soc_cs35l34 in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_SND|CONFIG_SND_SOC|CONFIG_SND_SOC_CS35L34' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code. In 5 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

• bookworm, trixie, forky, sid, bookworm · linux-6.12n

n

not enabled on any flavour - this release does not build the code

Build switches

CONFIG_SND, CONFIG_SND_SOC, CONFIG_SND_SOC_CS35L34

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-09-16 (33 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.21%, higher than 10.6% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

sound/soc

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
4.10	5.10.270	3be8380fb14d
4.10	5.15.221	96982734e765
4.10	6.1.188	5b0637396199
4.10	6.6.157	f4bfd755c52d
4.10	6.12.110	4fe8a91a9266
4.10	6.18.51	5a4fe7a87841
4.10	7.2.5	07a86575edc3
4.10	7.3	4105a4c0678b

Debian advisories