Skip to main content

Linux Kernel EUVDEUVD-2026-49004

| CVE-2026-64292 MEDIUM
Memory Leak (CWE-401)
2026-07-25 Linux GHSA-gr72-p8g3-6gpc
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local access and low privileges required to invoke iommufd API; impact is purely availability via atomic memory pool exhaustion, with no confidentiality or integrity consequence.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
5.5 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 12, 2026 - 15:08 vuln.today
CVSS changed
Aug 12, 2026 - 15:07 NVD
5.5 (MEDIUM)
Patch available
Jul 25, 2026 - 11:18 EUVD
CVE Published
Jul 25, 2026 - 08:49 nvd
MEDIUM 5.5
CVE Published
Jul 25, 2026 - 08:49 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

iommufd: Move vevent memory allocation outside spinlock

The veventq memory allocation happens inside the spinlock. Given its depth is decided by the user space, this leaves a vulnerability, where userspace can allocate large queues to exhaust atomic memory reserves.

Move the allocation outside the spinlock and use GFP_NOWAIT, which can fail fast under memory pressure without dipping into the GFP_ATOMIC reserves or direct-reclaiming from the threaded IRQ handler. On allocation failure, queue the lost_events_header (so userspace learns of the drop) and return -ENOMEM so the caller learns of the kernel-side memory pressure.

This is intentionally distinct from the queue-overflow path, which also queues the lost_events_header but returns 0: a full queue is an expected userspace-pacing condition rather than a kernel error.

A subsequent change will cap the upper bound of the veventq_depth.

AnalysisAI

Atomic memory reserve exhaustion in the Linux kernel's iommufd subsystem allows a local low-privileged user to trigger kernel-side memory pressure by allocating virtual event queues whose depth is fully user-controlled, potentially destabilizing the system through GFP_ATOMIC reserve depletion. The root cause is memory allocation for veventq entries occurring inside a spinlock, drawing from atomic reserves never intended for user-directed exhaustion. No active exploitation is confirmed and EPSS sits at 0.21% (11th percentile); upstream fix commits are available across the 6.18.x, 7.1.x, and 7.2-rc1 stable series.

Technical ContextAI

The iommufd (I/O Memory Management Unit File Descriptor) subsystem manages IOMMU resources for virtual machine device passthrough and related isolation workloads. Within iommufd, the virtual event queue (veventq) mechanism allows user space to receive IOMMU events asynchronously; the veventq_depth parameter, which governs maximum queue entries, is user-supplied. The vulnerability arises because memory allocation for new queue entries was performed inside a spinlock using GFP_ATOMIC semantics. GFP_ATOMIC draws from a reserved memory pool intended for interrupt-context allocations that cannot sleep; when user space repeatedly triggers this path with large depth values, these reserves can be exhausted, starving legitimate interrupt handlers. CWE-401 (Missing Release of Memory after Effective Lifetime) characterizes the improper memory management lifecycle. The fix relocates the allocation outside the spinlock and substitutes GFP_NOWAIT, which fails fast under pressure without touching atomic reserves or invoking direct reclaim from threaded IRQ context. The CPE identifier cpe:2.3:a:linux:linux covers the affected codebase. The 'Buffer Overflow' tag in source intelligence is a mis-categorization; this is a memory exhaustion issue, not a spatial safety violation.

RemediationAI

Upgrade to a patched kernel version: Linux 6.18.40, 7.1.4, or 7.2-rc1 or later, incorporating fix commits available at https://git.kernel.org/stable/c/779480ea79551c31964e74b9aef0e730faa3aa11, https://git.kernel.org/stable/c/47443565d10c51366c9382dbc8597cd6c460b8a2, and https://git.kernel.org/stable/c/6c5fc40200cd0a87d66a368eee00df4d1cca946e. Distribution vendors (Red Hat, Debian, Ubuntu, SUSE) will backport these fixes to their supported kernel branches; consult each vendor's security advisory portal for package-level patch availability. As a compensating control prior to patching, restrict unprivileged local user access to iommufd device interfaces via udev rules or file permission hardening on /dev/iommu and related nodes - note this may break legitimate VM device-passthrough or VFIO workloads and should be tested in non-production environments first. A subsequent upstream kernel change will additionally cap the upper bound of veventq_depth, providing a secondary guard against this class of user-controlled exhaustion.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

Share

EUVD-2026-49004 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy