CVE-2026-64481

What the bug is

cs35l41_hda creates ALSA controls whose private data points at the cs35l41_hda object. The firmware load control can also queue fw_load_work. Those controls are not removed on component unbind, and device remove only cancels fw_load_work through cs35l41_remove_dsp(). That helper is skipped when halo_initialized is false. With firmware_autostart disabled, a firmware load can be requested before the DSP has been initialized. If the component or device is removed before the queued work runs, the worker can run after teardown and dereference driver state that is no longer valid. Track the created controls and remove them on unbind so no new control callback can reach the driver data or queue more work. Then cancel fw_load_work to drain any request that was already queued. Also cancel the work unconditionally during device remove before runtime PM teardown.

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/hda/codecs/side-codecs/cs35l41_hda.c
sound/hda/codecs/side-codecs/cs35l41_hda.h

What this is

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

Kernel module

snd_hda_scodec_cs35l41

Check it on the machine

grep -wE 'CONFIG_SND|CONFIG_SND_HDA|CONFIG_SND_HDA_SCODEC_CS35L41' /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.

lsmod | grep -w snd_hda_scodec_cs35l41

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 3 releases, so nothing is claimed about those.

• bookworm, trixie?
• forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
• bookworm · linux-6.12?

?

not established - no Makefile entry for the affected file

M

a module where it is built at all; some flavours do not build it

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

Build switches

CONFIG_SND, CONFIG_SND_HDA, CONFIG_SND_HDA_SCODEC_CS35L41

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-07-25 (3 months ago)source

CVSS

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it

Attack vector

local (AV:L)source

EPSS

0.14%, higher than 2.9% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

sound/hda

Upstream fixes

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

Introduced	Fixed in	Commit
6.0	6.12.97	8947215c0136
6.0	6.18.39	ce0a903d0591
6.0	7.1.4	d6a40a4d083e
6.0	7.2	b65020d5398f

Debian advisories