CVE-2026-31581

HIGHCVSS · not yet scored7.8
EchelonGraph scoreLOW confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ALSA: 6fire: fix use-after-free on disconnect

In usb6fire_chip_abort(), the chip struct is allocated as the card's private data (via snd_card_new with sizeof(struct sfire_chip)). When snd_card_free_when_closed() is called and no file handles are open, the card and embedded chip are freed synchronously. The subsequent chip->card = NULL write then hits freed slab memory.

Call trace: usb6fire_chip_abort sound/usb/6fire/chip.c:59 [inline] usb6fire_chip_disconnect+0x348/0x358 sound/usb/6fire/chip.c:182 usb_unbind_interface+0x1a8/0x88c drivers/usb/core/driver.c:458 ... hub_event+0x1a04/0x4518 drivers/usb/core/hub.c:5953

Fix by moving the card lifecycle out of usb6fire_chip_abort() and into usb6fire_chip_disconnect(). The card pointer is saved in a local before any teardown, snd_card_disconnect() is called first to prevent new opens, URBs are aborted while chip is still valid, and snd_card_free_when_closed() is called last so chip is never accessed after the card may be freed.

CVSS v3
—
EG Score
7.8(low)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (9)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e88354b381e2006de63d6b052ed7005c9a47d00e
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e719232f4552e29de8027a83918ea94434be87af
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e247a0e01d15ed420f77ec5e2335721bf430a5b3
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d21e8a2af4869b5890b34e081d5aeadc93e9cd5c
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba88461f7653636c48321ca993006a74724c2f41
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b9c826916fdce6419b94eb0cd8810fdac18c2386
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/af75b486f7e883e3422ece23c8d727e6815144a0
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51f6532790b74ffdd6970bc848358a2838c1c185
generic

ALSA: 6fire: fix use-after-free on disconnect - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3dc20d1981d6a67d8184498a5da272942dde1e65

Vendor Advisories for CVE-2026-31581(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.22.1.el10_22026-06-11redhat
redhatkernel-0:5.14.0-687.15.1.el9_82026-06-11redhat
redhatkernel-rt-0:4.18.0-553.132.1.rt7.473.el8_102026-06-10redhat
redhatkernel-0:4.18.0-553.132.1.el8_102026-06-10redhat
linuxKernel @ 5.10.258—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (129 versions)6.19.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(21)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 254 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-04 03:16 UTCOSV refresh
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-24 14:17 UTCEPSS rescore
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 14:52 UTCEG score recompute
  7. 2026-08-17 14:52 UTCVendor advisory
  8. 2026-08-17 14:52 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 05:48 UTCEG score recompute
  12. 2026-08-16 05:48 UTCVendor advisory
  13. 2026-08-16 05:48 UTCGHSA enrichment
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 02:17 UTCEG score recompute
  16. 2026-08-15 02:17 UTCVendor advisory
  17. 2026-08-15 02:16 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 15:12 UTCVendor advisory
  20. 2026-08-14 15:12 UTCGHSA enrichment
  21. 2026-08-14 04:08 UTCEG score recompute
  22. 2026-08-14 04:08 UTCVendor advisory
  23. 2026-08-14 04:08 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 04:56 UTCVendor advisory
  26. 2026-08-13 04:56 UTCGHSA enrichment
  27. 2026-08-12 17:52 UTCEG score recompute
  28. 2026-08-12 17:52 UTCVendor advisory
  29. 2026-08-12 17:52 UTCGHSA enrichment
  30. 2026-08-12 13:50 UTCEPSS rescore
  31. 2026-08-11 16:42 UTCEG score recompute
  32. 2026-08-11 16:42 UTCVendor advisory
  33. 2026-08-11 16:41 UTCGHSA enrichment
  34. 2026-08-11 02:10 UTCEG score recompute
  35. 2026-08-11 02:10 UTCVendor advisory
  36. 2026-08-11 02:10 UTCGHSA enrichment
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-10 12:47 UTCVendor advisory
  39. 2026-08-10 12:47 UTCGHSA enrichment
  40. 2026-08-10 01:29 UTCVendor advisory
  41. 2026-08-10 01:29 UTCGHSA enrichment
  42. 2026-08-09 14:25 UTCEG score recompute
  43. 2026-08-09 14:25 UTCVendor advisory
  44. 2026-08-09 14:24 UTCGHSA enrichment
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-09 03:20 UTCEG score recompute
  47. 2026-08-09 03:20 UTCVendor advisory
  48. 2026-08-09 03:20 UTCGHSA enrichment
  49. 2026-08-08 16:37 UTCEPSS rescore
  50. 2026-08-08 11:11 UTCVendor advisory
  51. 2026-08-08 11:11 UTCGHSA enrichment
  52. 2026-08-07 23:39 UTCEG score recompute
  53. 2026-08-07 23:39 UTCVendor advisory
  54. 2026-08-07 23:39 UTCGHSA enrichment
  55. 2026-08-07 12:36 UTCVendor advisory
  56. 2026-08-07 12:36 UTCGHSA enrichment
  57. 2026-08-06 21:19 UTCEG score recompute
  58. 2026-08-06 21:19 UTCVendor advisory
  59. 2026-08-06 21:19 UTCGHSA enrichment
  60. 2026-08-06 13:46 UTCEPSS rescore
  61. 2026-08-06 10:15 UTCVendor advisory
  62. 2026-08-06 10:15 UTCGHSA enrichment
  63. 2026-08-05 22:57 UTCEG score recompute
  64. 2026-08-05 22:57 UTCVendor advisory
  65. 2026-08-05 22:57 UTCGHSA enrichment
  66. 2026-08-05 19:17 UTCEPSS rescore
  67. 2026-08-04 15:10 UTCEPSS rescore
  68. 2026-08-04 10:38 UTCEPSS rescore
  69. 2026-08-03 21:03 UTCEG score recompute
  70. 2026-08-03 21:03 UTCVendor advisory
  71. 2026-08-03 21:03 UTCGHSA enrichment
  72. 2026-08-03 10:36 UTCEPSS rescore
  73. 2026-08-02 22:26 UTCVendor advisory
  74. 2026-08-02 22:26 UTCGHSA enrichment
  75. 2026-08-02 11:22 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2026-31581?
CVE-2026-31581 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: 6fire: fix use-after-free on disconnect In usb6firechipabort(), the chip struct is allocated as the card's private data (via sndcardnew with sizeof(struct sfire_chip)). When sndcardfreewhenclosed() is called and no file…
When was CVE-2026-31581 disclosed?
CVE-2026-31581 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31581 actively exploited?
CVE-2026-31581 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
How do I remediate CVE-2026-31581?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31581, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31581

Explore →

Is Your Infrastructure Affected by CVE-2026-31581?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs