CVE-2026-72138

xen/gntdev: fix error handling in ioctl

N/A
Published: August 15, 2026 at 05:53 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: xen/gntdev: fix error handling in ioctl When gntdev_ioctl_map_grant_ref() fails to copy the operation result back to userspace after successfully adding the mapping to the list, the error path returns -EFAULT without releasing the reference acquired by gntdev_alloc_map(). The mapping remains in priv->maps with a refcount of 1, causing a memory leak and a dangling list entry. Additionally, gntdev_add_map() may modify map->index to avoid overlap with existing mappings. Therefore, the index returned to userspace must be obtained after gntdev_add_map() completes. Fix this by holding the mutex across gntdev_add_map(), retrieving the correct index, and copy_to_user(). If copy_to_user() fails, remove the mapping from the list and release the reference while still holding the lock. Fix these issues by properly handling all error cases.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.39 ≤ v < 5.10.2612.6.39 ≤ v < 5.15.2122.6.39 ≤ v < 6.1.1782.6.39 ≤ v < 6.12.972.6.39 ≤ v < 6.18.402.6.39 ≤ v < 6.6.1452.6.39 ≤ v < 7.1.52.6.39 ≤ v < 7.22.6.3968b025c813c2eb41ff25628e3d4952d5185eb1a4
Vendor states this is fixed in 16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454 (fixed)
Vendor states this is fixed in 18a693733f7ad004e1ab0466693121ca70cd95dd (fixed)
Vendor states this is fixed in 1dd9cb98fe228e017fff9efb33862ff38c741b65 (fixed)
Vendor states this is fixed in 311011f8cc206c5af2877b03e3f627ee1b8fe024 (fixed)
Vendor states this is fixed in 45ca1afe2fd14c04e37227e79d3f8455831d8408 (fixed)
Vendor states this is fixed in 52dc40ef0cfee6ae89b7524967e73f0ba37906d7 (fixed)
Vendor states this is fixed in 6883269a323609f68f6faa903f8f8ff3d191cec8 (fixed)
Vendor states this is fixed in 6df926130aee6cab9b5d2e5b7862e49ccac348dc (fixed)
Vendor states this is fixed in 2.6.39 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card