Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-31581: ALSA: 6fire: fix use-after-free on disconnect

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3dc20d1981d6a67d8184498a5da272942dde1e65, 4.20, 5.10.258.

Low priority for now. Upgrade to Linux Linux 3dc20d1981d6a67d8184498a5da272942dde1e65, 4.20, 5.10.258 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Apr 24, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31581

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 74357d0b5cd3ef544752bc9f21cbeee4902fae6c, 273eec23467dfbfbd0e4c10302579ba441fb1e13, 0df7f4b5cc10f5adf98be0845372e9eef7bb5b09, 6.13affected
    • f2d06d4e129e2508e356136f99bb20a332ff1a00 and later · before e719232f4552e29de8027a83918ea94434be87afaffected · git
    • b889a7d68d7e76b8795b754a75c91a2d561d5e8c and later · before e247a0e01d15ed420f77ec5e2335721bf430a5b3affected · git
    • ea8cc56db659cf0ae57073e32a4735ead7bd7ee3 and later · before ba88461f7653636c48321ca993006a74724c2f41affected · git
    • b754e831a94f82f2593af806741392903f359168 and later · before e88354b381e2006de63d6b052ed7005c9a47d00eaffected · git
    • 57860a80f03f9dc69a34a5c37b0941ad032a0a8c and later · before af75b486f7e883e3422ece23c8d727e6815144a0affected · git
    • a0810c3d6dd2d29a9b92604d682eacd2902ce947 and later · before d21e8a2af4869b5890b34e081d5aeadc93e9cd5caffected · git
    • a0810c3d6dd2d29a9b92604d682eacd2902ce947 and later · before 3dc20d1981d6a67d8184498a5da272942dde1e65affected · git
    • a0810c3d6dd2d29a9b92604d682eacd2902ce947 and later · before 51f6532790b74ffdd6970bc848358a2838c1c185affected · git
    • a0810c3d6dd2d29a9b92604d682eacd2902ce947 and later · before b9c826916fdce6419b94eb0cd8810fdac18c2386affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.22.1.el10_26.12.0-211.22.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31579Apr 24, 2026 · wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit
    22Monitor
  • ← EarlierCVE-2026-31580Apr 24, 2026 · bcache: fix cached_dev.sb_bio use-after-free and crash
    31Monitor
  • Later →CVE-2026-31582Apr 24, 2026 · hwmon: (powerz) Fix use-after-free on USB disconnect
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3dc20d1981d6a67d8184498a5da272942dde1e65Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux5.10.258Vendor (CNA)
Linux Linux5.15.209Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux51f6532790b74ffdd6970bc848358a2838c1c185Vendor (CNA)
Linux Linux6.1.175Vendor (CNA)
Linux Linux6.12Vendor (CNA)
Linux Linux6.12.83Vendor (CNA)
Linux Linux6.6.136Vendor (CNA)
Linux Linuxaf75b486f7e883e3422ece23c8d727e6815144a0Vendor (CNA)
Linux Linuxb9c826916fdce6419b94eb0cd8810fdac18c2386Vendor (CNA)
Linux Linuxba88461f7653636c48321ca993006a74724c2f41Vendor (CNA)
Linux Linuxd21e8a2af4869b5890b34e081d5aeadc93e9cd5cVendor (CNA)
Linux Linuxe247a0e01d15ed420f77ec5e2335721bf430a5b3Vendor (CNA)
Linux Linuxe719232f4552e29de8027a83918ea94434be87afVendor (CNA)
Linux Linuxe88354b381e2006de63d6b052ed7005c9a47d00eVendor (CNA)
almalinux:bpftool4.18.0-553.132.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.132.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.132.1.rt7.473.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)

+15

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records