In the Linux kernel, the following vulnerability has been resolved: vhost_iotlb: bound map allocation in add_range vhost_iotlb_add_range_ctx() only… (CVE-2026-74713)
A vulnerability in the Linux kernel's vhost_iotlb component was resolved, where the allocation of bound map entries in the add_range function could exceed configured limits under certain conditions. This flaw allowed non-retiring IOTLB tables to allocate entries beyond their set maximum, potentially leading to resource exhaustion or inconsistent state. The fix involves stricter enforcement of entry limits, rejecting invalid configurations, and improved handling of full-range mappings to prevent partial updates. The patch also optimizes memory reuse to avoid unnecessary allocations once limits are reached.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's vhost_iotlb subsystem involved improper enforcement of maximum entry limits in the vhost_iotlb_add_range_ctx() function. Specifically, non-retiring IOTLB tables could continue allocating entries after reaching their configured limit because the function only retired old entries when certain conditions were met. The patch corrects this by using the caller-provided limit for allocation, rejecting non-positive limits, and ensuring that full-range mappings are only inserted if both split entries can fit. Additionally, it reuses retired map nodes to prevent repeated memory allocations under high update loads. This resolves the risk of resource exhaustion and inconsistent IOTLB state due to unchecked entry allocation.
Potential Impact
The vulnerability could allow vhost devices using IOTLB tables without proper entry retirement to allocate entries beyond their configured limits. This may lead to resource exhaustion or inconsistent internal state within the kernel's IOTLB management, potentially affecting system stability or performance. No known exploits in the wild have been reported. The impact is primarily on kernel resource management in virtualized environments using vhost devices.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to enforce proper limits on IOTLB entry allocation and to reject invalid configurations. Users should update to a kernel version that includes this patch once available. Since this is a kernel-level vulnerability, applying the official kernel update is the recommended remediation. No additional mitigations are indicated by the vendor advisory.
In the Linux kernel, the following vulnerability has been resolved: vhost_iotlb: bound map allocation in add_range vhost_iotlb_add_range_ctx() only… (CVE-2026-74713)
Description
A vulnerability in the Linux kernel's vhost_iotlb component was resolved, where the allocation of bound map entries in the add_range function could exceed configured limits under certain conditions. This flaw allowed non-retiring IOTLB tables to allocate entries beyond their set maximum, potentially leading to resource exhaustion or inconsistent state. The fix involves stricter enforcement of entry limits, rejecting invalid configurations, and improved handling of full-range mappings to prevent partial updates. The patch also optimizes memory reuse to avoid unnecessary allocations once limits are reached.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's vhost_iotlb subsystem involved improper enforcement of maximum entry limits in the vhost_iotlb_add_range_ctx() function. Specifically, non-retiring IOTLB tables could continue allocating entries after reaching their configured limit because the function only retired old entries when certain conditions were met. The patch corrects this by using the caller-provided limit for allocation, rejecting non-positive limits, and ensuring that full-range mappings are only inserted if both split entries can fit. Additionally, it reuses retired map nodes to prevent repeated memory allocations under high update loads. This resolves the risk of resource exhaustion and inconsistent IOTLB state due to unchecked entry allocation.
Potential Impact
The vulnerability could allow vhost devices using IOTLB tables without proper entry retirement to allocate entries beyond their configured limits. This may lead to resource exhaustion or inconsistent internal state within the kernel's IOTLB management, potentially affecting system stability or performance. No known exploits in the wild have been reported. The impact is primarily on kernel resource management in virtualized environments using vhost devices.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to enforce proper limits on IOTLB entry allocation and to reject invalid configurations. Users should update to a kernel version that includes this patch once available. Since this is a kernel-level vulnerability, applying the official kernel update is the recommended remediation. No additional mitigations are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5mqx-jw5r-hp6c
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74713"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f0acd9273b499bc714
Added to database: 08/22/2026, 22:51:28 UTC
Last enriched: 08/23/2026, 00:39:31 UTC
Last updated: 08/23/2026, 02:31:59 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.