LIVE · cybersecurity feed
Live wire
CVE-2026-81578 · PaperCut NG/MF Flaw Exploited Before CVE PublicationCVE-2026-82078 · PaperCut NG/MF Flaw Exploited Before CVE PublicationCVE-2026-83549 · SonicWall SMA1000 OS Command Injection Exploited Same Day as DisclosureCVE-2026-83548 · SonicWall SMA1000 SSRF Flaw Exploited Same Day as DisclosureCVE-2026-82329 · JFrog Artifactory Flaw Exploited Same Day as DisclosureOpenAI Announced $1B in Defensive Tools for Water UtilitiesAttackers Breached JetBrains Cadence via Unpatched TeamCity, Extracting AWS CredentialsCVE-2026-59346 · Critical VMware Workstation and Fusion Flaw Lets VM Admins Execute Host CodeCVE-2026-32475 · Elementor Pro WordPress Plugin Vulnerability Exploited to Hack SitesBroadcom Patches Critical VMware Workstation and Fusion VM-Escape Vulnerabilities
cve recordhigh

CVE-2026-74713

Published
CVSS7.1
Severityhigh
Weakness
ExploitedNot in CISA KEV

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

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. Othe

References

← Back to the CVE Tracker

Our coverage of CVE-2026-74713

No stories yet. This page updates automatically when we publish reporting that references CVE-2026-74713.