Vulnerability · Published Apr 5, 2024 · Assigned by Linux
CVE-2024-26812vfio/pci: Create persistent INTx handler
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.2% (higher than 17% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than registration of a particular trigger eventfd. Synchronization is added between the ioctl path and eventfd_signal() wrapper such that the eventfd trigger can be dynamically updated relative to in-flight interrupts or irqfd callbacks.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.85-1 | DSA-5658-1 |
| Debian:12 | linux | 6.1.85-1 | DEBIAN-CVE-2024-26812 |
| Debian:13 | linux | 6.7.12-1 | DEBIAN-CVE-2024-26812 |
| Debian:14 | linux | 6.7.12-1 | DEBIAN-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux | 5.15.0-116.126 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux | 5.15.0-116.126 | USN-6898-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-35.35 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux | 6.8.0-35.35 | USN-6816-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1065.71 | USN-6898-3 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1065.71 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1009.9 | USN-6817-1 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1009.9 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1068.77 | USN-6917-1 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1068.77 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1008.8 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1008.8 | USN-6817-3 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1068.77.1 | USN-6917-1 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1068.77.1 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1064.72 | USN-6898-1 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1064.72 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1008.9 | USN-6817-1 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1008.9 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1062.68 | USN-6898-1 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1062.68 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1004.7 | USN-6817-3 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1004.7 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1048.55 | USN-6898-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1048.55 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1058.61 | USN-6898-1 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1058.61 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1006.6 | USN-6816-1 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1006.6 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1060.66 | USN-6898-1 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1060.66 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1062.67 | USN-6898-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1062.67 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-116.126 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-116.126 | USN-6898-2 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-35.35.1 | USN-6816-1 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-35.35.1 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1060.61 | USN-6898-1 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1060.61 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1026.26 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1015.15 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1006.6 | USN-6817-2 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1006.6 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1063.69 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1063.69 | USN-6898-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1006.6 | USN-6878-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1006.6 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1058.61 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1005.5 | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1005.5 | USN-6816-1 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-35.35.1 | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-26812 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1035.39 | USN-7019-1 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1035.39 | UBUNTU-CVE-2024-26812 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – before b18fa894d615c8527e15d96b76c7448800e1389989e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – before 27d40bf72dd9a6600b76ad05859176ea9a1b489789e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – before 4cb0d7532126d23145329826c38054b4e9a05e7c89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – before 7d29d4c72c1e196cce6969c98072a272d1a703b389e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – before 69276a555c740acfbff13fb5769ee9c92e1c828e89e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – before 4c089cefe30924fbe20dd1ee92774ea1f5eca83489e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – before 0e09cf81959d9f12b75ad5c6dd53d237432ed03489e1f7d4c66d85f42c3d52ea3866eb10cadf6153 – before 18c198c96a815c962adc2b9b77909eec0be7df4d |
| Linux | Linux | 3.6 |
References
- https://git.kernel.org/stable/c/b18fa894d615c8527e15d96b76c7448800e13899
- https://git.kernel.org/stable/c/27d40bf72dd9a6600b76ad05859176ea9a1b4897
- https://git.kernel.org/stable/c/4cb0d7532126d23145329826c38054b4e9a05e7c
- https://git.kernel.org/stable/c/7d29d4c72c1e196cce6969c98072a272d1a703b3
- https://git.kernel.org/stable/c/69276a555c740acfbff13fb5769ee9c92e1c828e
- https://git.kernel.org/stable/c/4c089cefe30924fbe20dd1ee92774ea1f5eca834
- https://git.kernel.org/stable/c/0e09cf81959d9f12b75ad5c6dd53d237432ed034
- https://git.kernel.org/stable/c/18c198c96a815c962adc2b9b77909eec0be7df4d
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html x_transferred
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html