CVE-2026-72138: Linux kernel · xen/gntdev: fix error handling in ioctl
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 6883269a323609f68f6faa903f8f8ff3d191cec8 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:19 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in 6883269a323609f68f6faa903f8f8ff3d191cec8, 311011f8cc206c5af2877b03e3f627ee1b8fe024, 52dc40ef0cfee6ae89b7524967e73f0ba37906d7 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/52dc40ef0cfee6ae89b7524967e73f0ba37906d7 (opens in a new tab)
- git.kernel.org/stable/c/1dd9cb98fe228e017fff9efb33862ff38c741b65 (opens in a new tab)
- git.kernel.org/stable/c/6df926130aee6cab9b5d2e5b7862e49ccac348dc (opens in a new tab)
- git.kernel.org/stable/c/311011f8cc206c5af2877b03e3f627ee1b8fe024 (opens in a new tab)
- git.kernel.org/stable/c/18a693733f7ad004e1ab0466693121ca70cd95dd (opens in a new tab)
- git.kernel.org/stable/c/16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454 (opens in a new tab)
- git.kernel.org/stable/c/6883269a323609f68f6faa903f8f8ff3d191cec8 (opens in a new tab)
- git.kernel.org/stable/c/45ca1afe2fd14c04e37227e79d3f8455831d8408 (opens in a new tab)