CVE-2026-74713
vhost_iotlb: bound map allocation in add_range
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.
INFO
Published Date :
Aug. 22, 2026, 4:16 p.m.
Last Modified :
Oct. 30, 2026, 1:20 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Update the Linux kernel to the latest version.
- Apply the specific patch for vhost_iotlb.
- Configure IOTLB with appropriate limits.
- Review vhost device configurations.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-74713.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-74713 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-74713
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-74713 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-74713 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 30, 2026
Action Type Old Value New Value Added Affected Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/74xxx/CVE-2026-74713.json">CVE-2026-74713</a> Added Reference https://git.kernel.org/stable/c/91d3f1fcb8f7109f18d46a7366bb8202ac4b4456 -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 21, 2026
Action Type Old Value New Value Added Affected Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/74xxx/CVE-2026-74713.json">CVE-2026-74713</a> Added Reference https://git.kernel.org/stable/c/96da3e1439e7d689eea09fc9b6227fbab5b88ac3 Added Reference https://git.kernel.org/stable/c/eb70200e34772572ad08e99291b08afea6522111 -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Oct. 16, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-74713', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-10-16T19:15:21.643384Z'} -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 15, 2026
Action Type Old Value New Value Added Affected Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/74xxx/CVE-2026-74713.json">CVE-2026-74713</a> Added Reference https://git.kernel.org/stable/c/1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94 Added Reference https://git.kernel.org/stable/c/ae128dd19040ee06a4f8143c7ced4d18080d7a9a Added Reference https://git.kernel.org/stable/c/b57164cdddb46924ff9fa191b727ca097744de88 Removed Reference https://git.kernel.org/stable/c/1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94 Removed Reference https://git.kernel.org/stable/c/ae128dd19040ee06a4f8143c7ced4d18080d7a9a -
CVE Translated by [email protected]
Oct. 14, 2026
Action Type Old Value New Value Added Translation Title: Linux, Description: En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta: vhost_iotlb: asignación de mapa limitada en add_range vhost_iotlb_add_range_ctx() solo retira una entrada antigua cuando la tabla tiene un límite no nulo, ha alcanzado exactamente ese límite y tiene VHOST_IOTLB_FLAG_RETIRE establecido. Las tablas que no retiran pueden seguir asignando entradas después de alcanzar su límite configurado. Los dispositivos vhost existentes asignan su IOTLB con max_iotlb_entries de vhost.c, que por defecto es 2048 y es configurable mediante un parámetro de módulo. Utilice el límite proporcionado por el llamador en el punto de asignación en lugar de añadir un valor predeterminado separado en el asistente IOTLB común, y rechace los valores no positivos en las rutas vhost que pueden informar un error. Otros usuarios de IOTLB de vhost no deben crear tablas de límite cero cuando las entradas pueden ser pobladas desde el espacio de usuario o solicitudes controladas por el invitado. Añada parámetros max_iotlb_entries del lado del llamador para mlx5 vDPA, VDUSE y vhost-vDPA. Rechace los valores no positivos de VDUSE y vhost-vDPA, y requiera al menos dos entradas para las rutas vdpa_sim y mlx5 vDPA que instalan mapeos de rango completo, ya que esos mapeos se dividen en dos entradas IOTLB. Maneje los mapeos de rango completo en el asistente común verificando que el IOTLB puede contener ambas entradas divididas antes de insertar la primera mitad. Esto evita devolver un error después de dejar un mapeo a medias. Cuando la tabla está llena, mantenga el comportamiento de retiro existente para las tablas que retiran y devuelva -ENOSPC para las tablas que no retiran. Reutilice el nodo de mapa retirado en lugar de liberarlo y asignar un reemplazo, para que un flujo de actualizaciones de IOTLB no pueda seguir forzando asignaciones GFP_ATOMIC después de que la tabla haya alcanzado su límite. Si un IOTLB de límite cero aún llega al asistente común, trátelo como un error de configuración y devuelva -EINVAL. Encontré este error yo mismo, aunque el parche fue escrito con asistencia de IA. -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 25, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 22, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '0bbe30668d89ec8a309f28ced6d092c90fb23e8c', 'lessThan': 'ae128dd19040ee06a4f8143c7ced4d18080d7a9a', 'versionType': 'git'}, {'status': 'affected', 'version': '0bbe30668d89ec8a309f28ced6d092c90fb23e8c', 'lessThan': '1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94', 'versionType': 'git'}], 'programFiles': ['drivers/vdpa/mlx5/core/mlx5_vdpa.h', 'drivers/vdpa/mlx5/core/mr.c', 'drivers/vdpa/mlx5/core/resources.c', 'drivers/vdpa/vdpa_sim/vdpa_sim.c', 'drivers/vdpa/vdpa_user/iova_domain.c', 'drivers/vhost/iotlb.c', 'drivers/vhost/vdpa.c', 'drivers/vhost/vhost.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.7'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.7', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '7.1.9', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/vdpa/mlx5/core/mlx5_vdpa.h', 'drivers/vdpa/mlx5/core/mr.c', 'drivers/vdpa/mlx5/core/resources.c', 'drivers/vdpa/vdpa_sim/vdpa_sim.c', 'drivers/vdpa/vdpa_user/iova_domain.c', 'drivers/vhost/iotlb.c', 'drivers/vhost/vdpa.c', 'drivers/vhost/vhost.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94 Added Reference https://git.kernel.org/stable/c/ae128dd19040ee06a4f8143c7ced4d18080d7a9a