From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64041: ASoC: codecs: fs210x: fix possible buffer overflow
Date: Sun, 19 Jul 2026 17:38:23 +0200 [thread overview]
Message-ID: <2026071906-CVE-2026-64041-c0ad@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: codecs: fs210x: fix possible buffer overflow
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)
The Linux kernel CVE team has assigned CVE-2026-64041 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit 75611770177965ae902c87c96eace07542beff07 and fixed in 6.18.34 with commit 1ddf678bb75b6383c775ece61d40956c441d8a26
Issue introduced in 6.18 with commit 75611770177965ae902c87c96eace07542beff07 and fixed in 7.0.11 with commit 6daefdf1cd3c56483f61970a76c0ad6028e4118f
Issue introduced in 6.18 with commit 75611770177965ae902c87c96eace07542beff07 and fixed in 7.1 with commit 0d435a7ebcd4e97e47673c1ab6fb27f973a053ec
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-64041
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
sound/soc/codecs/fs210x.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/1ddf678bb75b6383c775ece61d40956c441d8a26
https://git.kernel.org/stable/c/6daefdf1cd3c56483f61970a76c0ad6028e4118f
https://git.kernel.org/stable/c/0d435a7ebcd4e97e47673c1ab6fb27f973a053ec
reply other threads:[~2026-07-19 15:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026071906-CVE-2026-64041-c0ad@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox