Vulnerability · Published May 27, 2026 · Assigned by Linux

CVE-2026-46036vfio/cdx: Serialize VFIO_DEVICE_SET_IRQS with a per-device mutex

High 7.8

In plain English

A high-severity 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.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.1%top 96.7% 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: vfio/cdx: Serialize VFIO_DEVICE_SET_IRQS with a per-device mutex vfio_cdx_set_msi_trigger() reads vdev->config_msi and operates on the vdev->cdx_irqs array based on its value, but provides no serialization against concurrent VFIO_DEVICE_SET_IRQS ioctls. Two callers can race such that one observes config_msi as set while another clears it and frees cdx_irqs via vfio_cdx_msi_disable(), resulting in a use-after-free of the cdx_irqs array. Add a cdx_irqs_lock mutex to struct vfio_cdx_device and acquire it in vfio_cdx_set_msi_trigger(), which is the single chokepoint through which all updates to config_msi, cdx_irqs, and msi_count flow, covering both the ioctl path and the close-device cleanup path. This keeps the test of config_msi atomic with the subsequent enable, disable, or trigger operations. Drop the pre-call !cdx_irqs test from vfio_cdx_irqs_cleanup() as part of this change: the optimization it provided is redundant with the !config_msi early-return inside vfio_cdx_msi_disable(), and leaving the test in place would be an unsynchronized read of state the new lock is meant to protect.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.86-1DEBIAN-CVE-2026-46036
Debian:14linux7.0.4-1DEBIAN-CVE-2026-46036
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux7.0.0-27.27UBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-aws7.0.0-1008.8UBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-gcp7.0.0-1007.7UBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-ibm7.0.0-1009.9UBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1013.13UBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1008.8UBUNTU-CVE-2026-46036
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-oracle7.0.0-1007.7UBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-raspi7.0.0-1014.14UBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46036
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-realtime7.0.0-27.27.1UBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46036
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-46036
Ubuntu:26.04:LTSlinux-riscv7.0.0-27.27.1UBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-46036
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-46036
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-46036

Affected products (as reported)

VendorProductVersions
Linux Linux 848e447e000c41894ff931dc7c004fd42c8840f8 – before ddf96e23c366c566283fce8377928851fa7f5e81848e447e000c41894ff931dc7c004fd42c8840f8 – before 7b436ade16cc81095d79b79f8efa3af0a4f5c5a2848e447e000c41894ff931dc7c004fd42c8840f8 – before 7530f34ec0ca1438d45a75dcb43183a1cc92eced848e447e000c41894ff931dc7c004fd42c8840f8 – before 670e8864b1a218d72f08db40d0103adf38fa1d9b
Linux Linux 6.10

References