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-98264ALSA: virtio: reset device before deleting virtqueues

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: virtio: reset device before deleting virtqueues virtsnd_remove() and virtsnd_freeze() delete the virtqueues before resetting the device. del_vqs() frees the vring backing, but does not provide a generic device quiesce operation. In particular, modern virtio-pci keeps enabled queues active until the device is reset. Reset the device before deleting the virtqueues so it can no longer access the vring memory when that memory is released. This also covers probe failures after DRIVER_OK, which unwind through virtsnd_remove().

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 24 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 93% of all CVEs (14 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 de3a9980d8c34b2479173e809afa820473db676a – < c0156a60adfb351b15ff25fbd76a0c639e96246c
    • affected de3a9980d8c34b2479173e809afa820473db676a – < 8edc3669e3e22f0123a1114c3a03df9abc4cd465
    • affected de3a9980d8c34b2479173e809afa820473db676a – < 830012feadc228a938514a6487862dcf56af7e66
    • affected de3a9980d8c34b2479173e809afa820473db676a – < 500a8401415ab085555785c3c339747e378abd36
    • affected de3a9980d8c34b2479173e809afa820473db676a – < 3e24b4a6acfd3bedb2200334595facd767c9a897
    • affected de3a9980d8c34b2479173e809afa820473db676a – < f070cce7cb361d5389b18f3ff6bd3d25a7596369
    • affected de3a9980d8c34b2479173e809afa820473db676a – < 6c05d00af307560e6a9f1631d6270d3df5aa2272
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .