Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31619, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < 183aa0de0f680496b9feb85c9d182681ad4600dd
    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < 62fcb273fbee5b2a0e7ed41cc914c8d7d1a5d285
    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < 327f8e730e3c65ec97df9d3b07de66aeb3dc932d
    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < f856f4b6efd51be7950e4b84c06cd961961ca41c
    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < e103f98f6615ed2934e9cf340654f0cad9eb8a8a
    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < 67cfd14074cdafab5de3f7cfc0952c1a9b653e5d
    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < cc624b3d2be13297100539b64ad950695188e046
    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < 682d8accf0d83a871e8c327b95c81f53902c922b
    • affected bde8a8f23bbe6db51fa4e81644273af18fef3d7a – < 07704bbf36f57e4379e4cadf96410dab14621e3b
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0.1 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31619 badge
[![CVE-2026-31619](https://cveledger.app/badge/CVE-2026-31619.svg)](https://cveledger.app/cve/CVE-2026-31619)

Record last updated .