Answer in brief
CVE-2026-98266 records a Unknown severity vulnerability in ALSA: core: Fix potential UAF after asynchronous card release. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5c0df40aa577e405c458e44e8d458dd78407f4af || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2dec4642589a663e064e4411d92d6e8fa250d53b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <398b21608955c9712a012355b69a39407367edc9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fd95e68df6fe66344161a1329cbe5e5805e7b704 || >=0 <6.12.112 || >=0 <6.18.54 || >=0 <7.2.8 | 5c0df40aa577e405c458e44e8d458dd78407f4af, 2dec4642589a663e064e4411d92d6e8fa250d53b, 398b21608955c9712a012355b69a39407367edc9, fd95e68df6fe66344161a1329cbe5e5805e7b704, 6.12.112, 6.18.54, 7.2.8 |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.