Skip to main content
VulnerabilityPublished Updated

CVE-2026-31619: Linux kernel · ALSA: fireworks: bound device-supplied status before string array lookup

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f856f4b6efd51be7950e4b84c06cd961961ca41c : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:04 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 24 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ bde8a8f23bbe6db51fa4e81644273af18fef3d7a, < f856f4b6efd51be7950e4b84c06cd961961ca41c
Fixed in
  • f856f4b6efd51be7950e4b84c06cd961961ca41c
LinuxLinuxAffected
  • ≥ bde8a8f23bbe6db51fa4e81644273af18fef3d7a, < e103f98f6615ed2934e9cf340654f0cad9eb8a8a
Fixed in
  • e103f98f6615ed2934e9cf340654f0cad9eb8a8a
LinuxLinuxAffected
  • ≥ bde8a8f23bbe6db51fa4e81644273af18fef3d7a, < cc624b3d2be13297100539b64ad950695188e046
Fixed in
  • cc624b3d2be13297100539b64ad950695188e046
LinuxLinuxAffected
  • ≥ bde8a8f23bbe6db51fa4e81644273af18fef3d7a, < 07704bbf36f57e4379e4cadf96410dab14621e3b
Fixed in
  • 07704bbf36f57e4379e4cadf96410dab14621e3b
LinuxLinuxAffected
  • ≥ bde8a8f23bbe6db51fa4e81644273af18fef3d7a, < 682d8accf0d83a871e8c327b95c81f53902c922b
Fixed in
  • 682d8accf0d83a871e8c327b95c81f53902c922b
LinuxLinuxAffected
  • ≥ bde8a8f23bbe6db51fa4e81644273af18fef3d7a, < 327f8e730e3c65ec97df9d3b07de66aeb3dc932d
Fixed in
  • 327f8e730e3c65ec97df9d3b07de66aeb3dc932d

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

Community reviews

Loading reviews…