Vulnerability · Published Jul 19, 2026 · Assigned by Linux
CVE-2026-64106KVM: arm64: vgic-its: Reject restored DTE with out-of-range num_eventid_bits
Critical 9.0
In plain English
A critical-severity improper input validation 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 4% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic-its: Reject restored DTE with out-of-range num_eventid_bits Userspace can restore an ITS Device Table Entry whose Size field encodes more EventID bits than the virtual ITS supports. The live MAPD path rejects that state, but vgic_its_restore_dte() accepts it and stores the out-of-range value in dev->num_eventid_bits. Reject restored DTEs with num_eventid_bits > VITS_TYPER_IDBITS before allocating the device. This mirrors the MAPD check and prevents the restored state from reaching vgic_its_restore_itt(), where the unchecked value can be converted into an oversized scan_its_table() range.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.176-1 | DEBIAN-CVE-2026-64106 |
| Debian:13 | linux | 6.12.94-1 | DEBIAN-CVE-2026-64106 |
| Debian:14 | linux | 7.0.12-1 | DEBIAN-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux | 6.8.0-139.139 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-139.139 | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux | 7.0.0-28.28 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1064.67 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1064.67 | USN-8729-6 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1009.9 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1064.67~22.04.1 | USN-8729-6 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1064.67~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1067.75 | USN-8761-1 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1067.75 | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1010.10 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1067.75~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1067.75~22.04.1 | USN-8761-3 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1065.72 | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1009.9 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1065.72~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1067.75 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1067.75 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1008.8 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1067.75~22.04.1 | USN-8729-3 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1067.75~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1062.70 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1062.70 | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1003.4 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1049.53 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1049.53 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-28.28~24.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1064.65 | USN-8729-3 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1064.65 | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1010.10 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1066.67~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-intel-iotg | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-kvm | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-139.139.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-139.139.1 | USN-8729-4 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-139.139.1~22.04.1 | USN-8729-4 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-139.139.1~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1062.65 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1062.65 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1016.16 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1062.65~22.04.1 | USN-8729-1 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1062.65~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2016.16 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1062.65.1 | USN-8729-1 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1062.65.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1035.38 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1009.9 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1061.64 | USN-8802-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1061.64 | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1008.8 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1061.64~22.04.1 | USN-8802-1 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1061.64~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1064.68 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1064.68 | USN-8729-1 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1015.15 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-28.28.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-28.28.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-139.139~22.04.1 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-28.28.1~24.04.3 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-vmware | 6.8.0-1008.8 | UBUNTU-CVE-2026-64106 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1036.37 | USN-8729-3 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1036.37 | UBUNTU-CVE-2026-64106 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | no fix listed | UBUNTU-CVE-2026-64106 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 57a9a117154c93539e33161dd318e6aeb8c04efa – before 1716b7fea2ead941a0dfac06c4504a3437cdf00d57a9a117154c93539e33161dd318e6aeb8c04efa – before dab9f93251b2c86a033de6098d0c73afddd55d4a57a9a117154c93539e33161dd318e6aeb8c04efa – before b94538186a3eae3763b8f96dacd610920a865aa757a9a117154c93539e33161dd318e6aeb8c04efa – before 0680f511926589206f81f57f76ce131d7741a31657a9a117154c93539e33161dd318e6aeb8c04efa – before 8bcd15b690a390241179516af1b6ae49ebfd9d9557a9a117154c93539e33161dd318e6aeb8c04efa – before 9ce754ed8e7ab4e3999767ce1505f85c449ccb07 |
| Linux | Linux | 4.12 |
Weakness: CWE-20 · Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:H
References
- https://git.kernel.org/stable/c/1716b7fea2ead941a0dfac06c4504a3437cdf00d
- https://git.kernel.org/stable/c/dab9f93251b2c86a033de6098d0c73afddd55d4a
- https://git.kernel.org/stable/c/b94538186a3eae3763b8f96dacd610920a865aa7
- https://git.kernel.org/stable/c/0680f511926589206f81f57f76ce131d7741a316
- https://git.kernel.org/stable/c/8bcd15b690a390241179516af1b6ae49ebfd9d95
- https://git.kernel.org/stable/c/9ce754ed8e7ab4e3999767ce1505f85c449ccb07