Vulnerability · Published Apr 5, 2024 · Assigned by Linux
CVE-2024-26814vfio/fsl-mc: Block calling interrupt handler without trigger
Medium 5.5
In plain English
A medium-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 13% 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/fsl-mc: Block calling interrupt handler without trigger The eventfd_ctx trigger pointer of the vfio_fsl_mc_irq object is initially NULL and may become NULL if the user sets the trigger eventfd to -1. The interrupt handler itself is guaranteed that trigger is always valid between request_irq() and free_irq(), but the loopback testing mechanisms to invoke the handler function need to test the trigger. The triggering and setting ioctl paths both make use of igate and are therefore mutually exclusive. The vfio-fsl-mc driver does not make use of irqfds, nor does it support any sort of masking operations, therefore unlike vfio-pci and vfio-platform, the flow can remain essentially unchanged.
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-26814 |
| Debian:13 | linux | 6.7.12-1 | DEBIAN-CVE-2024-26814 |
| Debian:14 | linux | 6.7.12-1 | DEBIAN-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux | 5.15.0-116.126 | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| 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-26814 |
| 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-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1008.8 | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| 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-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| 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-26814 |
| 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-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-116.126 | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1026.26 | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1015.15 | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1063.69 | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1058.61 | UBUNTU-CVE-2024-26814 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1005.5 | UBUNTU-CVE-2024-26814 |
| 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-26814 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-35.35.1 | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-26814 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-26814 |
| 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-26814 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | cc0ee20bd96971c10eba9a83ecf1c0733078a083 – before a563fc18583ca4f42e2fdd0c70c7c618288e7edecc0ee20bd96971c10eba9a83ecf1c0733078a083 – before 250219c6a556f8c69c5910fca05a59037e24147dcc0ee20bd96971c10eba9a83ecf1c0733078a083 – before 083e750c9f5f4c3bf61161330fb84d7c8e8bb417cc0ee20bd96971c10eba9a83ecf1c0733078a083 – before ee0bd4ad780dfbb60355b99f25063357ab488267cc0ee20bd96971c10eba9a83ecf1c0733078a083 – before de87511fb0404d23b6da5f4660383b6ed095e28dcc0ee20bd96971c10eba9a83ecf1c0733078a083 – before 6ec0d88166dac43f29e96801c0927d514f17add9cc0ee20bd96971c10eba9a83ecf1c0733078a083 – before 7447d911af699a15f8d050dfcb7c680a86f87012 |
| Linux | Linux | 5.10 |
References
- https://git.kernel.org/stable/c/a563fc18583ca4f42e2fdd0c70c7c618288e7ede
- https://git.kernel.org/stable/c/250219c6a556f8c69c5910fca05a59037e24147d
- https://git.kernel.org/stable/c/083e750c9f5f4c3bf61161330fb84d7c8e8bb417
- https://git.kernel.org/stable/c/ee0bd4ad780dfbb60355b99f25063357ab488267
- https://git.kernel.org/stable/c/de87511fb0404d23b6da5f4660383b6ed095e28d
- https://git.kernel.org/stable/c/6ec0d88166dac43f29e96801c0927d514f17add9
- https://git.kernel.org/stable/c/7447d911af699a15f8d050dfcb7c680a86f87012
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html x_transferred