Vulnerability · Published Aug 22, 2026 · Assigned by Linux

CVE-2026-74713vhost_iotlb: bound map allocation in add_range

High 7.1

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.1High
Exploit odds (30 days)0.1%top 96.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: vhost_iotlb: bound map allocation in add_range vhost_iotlb_add_range_ctx() only retires an old entry when the table has a non-zero limit, has exactly reached that limit and has VHOST_IOTLB_FLAG_RETIRE set. Non-retiring tables can keep allocating entries after reaching their configured limit. Existing vhost devices allocate their IOTLB with max_iotlb_entries from vhost.c, which defaults to 2048 and is tunable by module parameter. Use the caller-provided limit at the allocation point instead of adding a separate default in the common IOTLB helper, and reject non-positive values in vhost paths that can report an error. Other vhost IOTLB users should not create zero-limit tables when entries can be populated from userspace or guest-controlled requests. Add caller-side max_iotlb_entries parameters for mlx5 vDPA, VDUSE and vhost-vDPA. Reject non-positive VDUSE and vhost-vDPA values, and require at least two entries for vdpa_sim and mlx5 vDPA paths that install full-range mappings, since those mappings are split into two IOTLB entries. Handle full-range mappings in the common helper by checking that the IOTLB can hold both split entries before inserting the first half. This avoids returning an error after leaving a half mapping behind. When the table is full, keep the existing retire behavior for retiring tables and return -ENOSPC for non-retiring tables. Reuse the retired map node instead of freeing it and allocating a replacement, so a stream of IOTLB updates cannot keep forcing GFP_ATOMIC allocations after the table has reached its limit. If a zero-limit IOTLB still reaches the common helper, treat it as a configuration error and return -EINVAL. I found this bug myself, though the patch was written with AI assistance.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-74713
Debian:13linux6.12.115-2DEBIAN-CVE-2026-74713
Debian:14linux7.1.9-1DEBIAN-CVE-2026-74713
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1036.39UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-74713
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-74713
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-74713
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-74713

Affected products (as reported)

VendorProductVersions
Linux Linux 0bbe30668d89ec8a309f28ced6d092c90fb23e8c – before 91d3f1fcb8f7109f18d46a7366bb8202ac4b44560bbe30668d89ec8a309f28ced6d092c90fb23e8c – before 96da3e1439e7d689eea09fc9b6227fbab5b88ac30bbe30668d89ec8a309f28ced6d092c90fb23e8c – before eb70200e34772572ad08e99291b08afea65221110bbe30668d89ec8a309f28ced6d092c90fb23e8c – before b57164cdddb46924ff9fa191b727ca097744de880bbe30668d89ec8a309f28ced6d092c90fb23e8c – before ae128dd19040ee06a4f8143c7ced4d18080d7a9a0bbe30668d89ec8a309f28ced6d092c90fb23e8c – before 1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94
Linux Linux 5.7

References