CVE-2026-98266
ALSA: core: Fix potential UAF after asynchronous card release
No known exploitation. EPSS puts it in the 6th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 5c0df40aa577e405c458e44e8d458dd78407f4afUpgrade to: 5c0df40aa577e405c458e44e8d458dd78407f4afAffected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 2dec4642589a663e064e4411d92d6e8fa250d53bUpgrade to: 2dec4642589a663e064e4411d92d6e8fa250d53bAffected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 398b21608955c9712a012355b69a39407367edc9Upgrade to: 398b21608955c9712a012355b69a39407367edc9Affected: ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < fd95e68df6fe66344161a1329cbe5e5805e7b704Upgrade to: fd95e68df6fe66344161a1329cbe5e5805e7b704Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix potential UAF after asynchronous card release Usually a sound driver releases the resources assigned to the card via snd_card_free(), and it synchronizes with the whole release procedure. However, when the card is released asynchronously via snd_card_free_when_closed() like USB-audio driver, the situation is slightly different; although the snd_card_disconnect() call at the disconnection guarantees that any newer accesses will be gated, the in-flight tasks might be still accessing to the underlying card->dev device even after the disconnection, which would cause a use-after-free in the end, as reported by fuzzers. For addressing the bug above, this patch takes the refcount of card->dev at initialization of the card object, and releases at its destructor. This assures the availability of the card->dev in its whole lifecycle.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 6th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
3 events over 1 day, from the signal feeds we watch.
- Record updated
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/2dec4642589a663e064e4411d92d6e8fa250d53b
- git.kernel.org/stable/c/398b21608955c9712a012355b69a39407367edc9
- git.kernel.org/stable/c/5c0df40aa577e405c458e44e8d458dd78407f4af
And 1 more reference. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI