CVE-2026-31619: Linux kernel · ALSA: fireworks: bound device-supplied status before string array lookup
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f856f4b6efd51be7950e4b84c06cd961961ca41c : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:04 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 f856f4b6efd51be7950e4b84c06cd961961ca41c, e103f98f6615ed2934e9cf340654f0cad9eb8a8a, cc624b3d2be13297100539b64ad950695188e046 +6
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Apr 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: fireworks: bound device-supplied status before string array lookup The status field in an EFW response is a 32-bit value supplied by the firewire device. efr_status_names[] has 17 entries so a status value outside that range goes off into the weeds when looking at the %s value. Even worse, the status could return EFR_STATUS_INCOMPLETE which is 0x80000000, and is obviously not in that array of potential strings. Fix this up by properly bounding the index against the array size and printing "unknown" if it's not recognized.
References
- git.kernel.org/stable/c/183aa0de0f680496b9feb85c9d182681ad4600dd (opens in a new tab)
- git.kernel.org/stable/c/62fcb273fbee5b2a0e7ed41cc914c8d7d1a5d285 (opens in a new tab)
- git.kernel.org/stable/c/327f8e730e3c65ec97df9d3b07de66aeb3dc932d (opens in a new tab)
- git.kernel.org/stable/c/f856f4b6efd51be7950e4b84c06cd961961ca41c (opens in a new tab)
- git.kernel.org/stable/c/e103f98f6615ed2934e9cf340654f0cad9eb8a8a (opens in a new tab)
- git.kernel.org/stable/c/67cfd14074cdafab5de3f7cfc0952c1a9b653e5d (opens in a new tab)
- git.kernel.org/stable/c/cc624b3d2be13297100539b64ad950695188e046 (opens in a new tab)
- git.kernel.org/stable/c/682d8accf0d83a871e8c327b95c81f53902c922b (opens in a new tab)
- git.kernel.org/stable/c/07704bbf36f57e4379e4cadf96410dab14621e3b (opens in a new tab)