Vulnerability · Published Sep 25, 2026 · Assigned by Linux

CVE-2026-97996virtio: fix use-after-free in unregister_virtio_device()

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 93.9% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: virtio: fix use-after-free in unregister_virtio_device() device_unregister() is device_del() plus put_device(). When the caller holds no extra reference, that drops the last one and runs the release callback, which for several transports frees the memory the embedded struct virtio_device sits in. unregister_virtio_device() then calls virtio_debug_device_exit(), which reads dev->debugfs_dir out of the freed object. Affected transports are the ones whose release callback frees and whose remove path takes no reference: virtio_mmio, virtio_vdpa, virtio_uml, mlxbf-tmfifo and virtio_ccw. virtio_pci is unaffected because virtio_pci_remove() brackets the call with get_device() and put_device(). Remove the debugfs entries before the device can go away. They are only accessed through the protected debugfs interface, so debugfs_remove_recursive() waits for in-progress file operations before returning. Tearing them down while the device is still alive is therefore safe. Reproduced on User-Mode Linux with CONFIG_KASAN and CONFIG_VIRTIO_DEBUG by unbinding a virtio-uml device: BUG: KASAN: slab-use-after-free in virtio_debug_device_exit+0x36/0x4d Read of size 8 at addr 00000000616e0b10 by task init/1 __asan_report_load8_noabort virtio_debug_device_exit+0x36/0x4d unregister_virtio_device+0x48/0x75 virtio_uml_remove platform_remove device_release_driver_internal unbind_store Freed by task 1: kfree virtio_uml_release_dev device_release kobject_put put_device device_unregister With this applied, the report is gone and unbind is clean.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.111-1DEBIAN-CVE-2026-97996
Debian:14linux7.2.7-1DEBIAN-CVE-2026-97996
Debian:12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-97996
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-97996
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-97996
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-97996
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-97996

Affected products (as reported)

VendorProductVersions
Linux Linux 96a8326d69fffd7e8c2eb737dc060d8009a33b39 – before 951cad50cba89e736afdee4a730e0e52f9245c9b96a8326d69fffd7e8c2eb737dc060d8009a33b39 – before 77dbd10a701a30fdfea5c3bb7a29163128f9a9c796a8326d69fffd7e8c2eb737dc060d8009a33b39 – before caf042153016d651b55d0fb4a63cdf7d0d23dee296a8326d69fffd7e8c2eb737dc060d8009a33b39 – before 3f9a0fceb730f5107d52421ead5568eae25a0049
Linux Linux 6.10

References