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-98266ALSA: core: Fix potential UAF after asynchronous card release

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5c0df40aa577e405c458e44e8d458dd78407f4af
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2dec4642589a663e064e4411d92d6e8fa250d53b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 398b21608955c9712a012355b69a39407367edc9
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < fd95e68df6fe66344161a1329cbe5e5805e7b704
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .