CVE-2026-46088: Linux kernel · ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e0da8a8cac74f4b9f577979d131f0d2b88a84487 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in e0da8a8cac74f4b9f577979d131f0d2b88a84487, bfcbb4994da9e979c4bcfcf24aaaac69e457e48e, a470f7cabc4df72d9bd132f5719a8717292bb440 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: control: Validate buf_len before strnlen() in snd_ctl_elem_init_enum_names() snd_ctl_elem_init_enum_names() advances pointer p through the names buffer while decrementing buf_len. If buf_len reaches zero but items remain, the next iteration calls strnlen(p, 0). While strnlen(p, 0) returns 0 and would hit the existing name_len == 0 error path, CONFIG_FORTIFY_SOURCE's fortified strnlen() first checks maxlen against __builtin_dynamic_object_size(). When Clang loses track of p's object size inside the loop, this triggers a BRK exception panic before the return value is examined. Add a buf_len == 0 guard at the loop entry to prevent calling fortified strnlen() on an exhausted buffer. Found by kernel fuzz testing through Xiaomi Smartphone.
References
- git.kernel.org/stable/c/708f6ec9bcdf58bfd561409110baaf4fd3be4ea3 (opens in a new tab)
- git.kernel.org/stable/c/bfcbb4994da9e979c4bcfcf24aaaac69e457e48e (opens in a new tab)
- git.kernel.org/stable/c/a470f7cabc4df72d9bd132f5719a8717292bb440 (opens in a new tab)
- git.kernel.org/stable/c/1fbe46d2b72754d8bd580e13e59ccb5d3d0e8cb0 (opens in a new tab)
- git.kernel.org/stable/c/8ba0214c3dd32b8ec652947e3f2bc5b8f6e6be9e (opens in a new tab)
- git.kernel.org/stable/c/654c818a69c21d2bea4e8fd9eae7da865df9a5c8 (opens in a new tab)
- git.kernel.org/stable/c/82012fd3e78a14360fbc2f1a7491589896704f97 (opens in a new tab)
- git.kernel.org/stable/c/e0da8a8cac74f4b9f577979d131f0d2b88a84487 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)