CVE-2026-74713

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.

• https://git.kernel.org/stable/c/1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94
• https://git.kernel.org/stable/c/91d3f1fcb8f7109f18d46a7366bb8202ac4b4456
• https://git.kernel.org/stable/c/96da3e1439e7d689eea09fc9b6227fbab5b88ac3
• https://git.kernel.org/stable/c/ae128dd19040ee06a4f8143c7ced4d18080d7a9a
• https://git.kernel.org/stable/c/b57164cdddb46924ff9fa191b727ca097744de88
• https://git.kernel.org/stable/c/eb70200e34772572ad08e99291b08afea6522111

Published

Aug 22, 2026

Last Modified

Oct 30, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-74708In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74709In the Linux kernel, the following vulnerability has been re…
• CVE-2026-7471GitLab has remediated an issue in GitLab EE affecting all ve…3.5
• CVE-2026-74710In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74711In the Linux kernel, the following vulnerability has been re…8.4
• CVE-2026-74712In the Linux kernel, the following vulnerability has been re…9.3
• CVE-2026-74714In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74715In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74716In the Linux kernel, the following vulnerability has been re…
• CVE-2026-74717In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2026-74718In the Linux kernel, the following vulnerability has been re…
• CVE-2026-74719In the Linux kernel, the following vulnerability has been re…