Look up another CVE · open CVE-2026-64041 in the interactive tracker
CVE-2026-64041
ASoC: codecs: fs210x: fix possible buffer overflow
Published 2026-07-19 (3 months ago) by the Linux kernel CNA. Subsystem sound/soc. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-64041 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.12-1 | Update the kernel and reboot. Fixed in 7.0.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
In fs210x_effect_scene_info(), a string was copied like this: strscpy(DST, SRC, strlen(SRC) + 1); A buffer overflow would happen if strlen(SRC) >= sizeof(DST). Actually, strscpy() must be used this way: strscpy(DST, SRC, sizeof(DST)); strscpy(DST, SRC); // defaults to sizeof(DST)
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/fs210x.c
- What this is
- FOURSEMI AUDIO AMPLIFIER DRIVERMAINTAINERS section matched on sound/soc/codecs/fs210x.* · linux-sound@vger.kernel.org · Maintained
Check it on the machine
grep -wE 'CONFIG_SND|CONFIG_SND_SOC|CONFIG_SND_SOC_FS210X' /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 2 releases. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidn
- ?
- not established - no Makefile entry for the affected file
- n
- not enabled on any flavour - this release does not build the code
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_SOC, CONFIG_SND_SOC_FS210X
- 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-19 (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.19%, higher than 7.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- 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 |
|---|---|---|
| 6.18 | 6.18.34 | 1ddf678bb75b |
| 6.18 | 7.0.11 | 6daefdf1cd3c |
| 6.18 | 7.1 | 0d435a7ebcd4 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The overflow is triggered only through a local ALSA control ioctl on /dev/snd/controlC*, not via any network, Bluetooth, or physical bus interface.
- AC:LAttack complexity, low
- Once firmware contains a scene name of 64+ bytes, a single SNDRV_CTL_IOCTL_ELEM_INFO call deterministically overflows the 64-byte enumerated name buffer on the kernel stack.
- PR:LPrivileges required, low
- Exploitation requires local access to the ALSA control device, which is typically granted to unprivileged users in the audio group on embedded Linux, kiosk, and IoT deployments using this amplifier.
- UI:NUser interaction, none
- The attacker can trigger the vulnerable ioctl directly (e.g., via amixer or a custom program) without requiring any action from a victim user.
- S:UScope, unchanged
- Successful exploitation results in standard kernel memory corruption and potential local privilege escalation within the same security authority, not a cross-boundary escape such as VM or sandbox breakout.
- C:HConfidentiality impact, high
- The stack buffer overflow writes beyond the 64-byte destination, corrupting adjacent kernel stack data and enabling information disclosure as part of memory corruption exploitation.
- I:HIntegrity impact, high
- Unbounded stack corruption from the incorrect strscpy size argument can overwrite return addresses and other stack metadata, enabling arbitrary kernel code execution.
- A:HAvailability impact, high
- Stack corruption in kernel context during ioctl handling can cause kernel oops, panic, or hang, resulting in complete loss of system availability.