Answer in brief
CVE-2026-72138 records a Unknown severity vulnerability in xen/gntdev: fix error handling in ioctl. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72138 records a Unknown severity vulnerability in xen/gntdev: fix error handling in ioctl. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <52dc40ef0cfee6ae89b7524967e73f0ba37906d7 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <1dd9cb98fe228e017fff9efb33862ff38c741b65 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <6df926130aee6cab9b5d2e5b7862e49ccac348dc || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <311011f8cc206c5af2877b03e3f627ee1b8fe024 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <18a693733f7ad004e1ab0466693121ca70cd95dd || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <6883269a323609f68f6faa903f8f8ff3d191cec8 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <45ca1afe2fd14c04e37227e79d3f8455831d8408 | 52dc40ef0cfee6ae89b7524967e73f0ba37906d7, 1dd9cb98fe228e017fff9efb33862ff38c741b65, 6df926130aee6cab9b5d2e5b7862e49ccac348dc, 311011f8cc206c5af2877b03e3f627ee1b8fe024, 18a693733f7ad004e1ab0466693121ca70cd95dd, 16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454, 6883269a323609f68f6faa903f8f8ff3d191cec8, 45ca1afe2fd14c04e37227e79d3f8455831d8408 |
| Linux/Linuxgeneric | 2.6.39 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <52dc40ef0cfee6ae89b7524967e73f0ba37906d7 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <1dd9cb98fe228e017fff9efb33862ff38c741b65 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <6df926130aee6cab9b5d2e5b7862e49ccac348dc || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <311011f8cc206c5af2877b03e3f627ee1b8fe024 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <18a693733f7ad004e1ab0466693121ca70cd95dd || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <6883269a323609f68f6faa903f8f8ff3d191cec8 || >=68b025c813c2eb41ff25628e3d4952d5185eb1a4 <45ca1afe2fd14c04e37227e79d3f8455831d8408 | 52dc40ef0cfee6ae89b7524967e73f0ba37906d7, 1dd9cb98fe228e017fff9efb33862ff38c741b65, 6df926130aee6cab9b5d2e5b7862e49ccac348dc, 311011f8cc206c5af2877b03e3f627ee1b8fe024, 18a693733f7ad004e1ab0466693121ca70cd95dd, 16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454, 6883269a323609f68f6faa903f8f8ff3d191cec8, 45ca1afe2fd14c04e37227e79d3f8455831d8408 |
| Linux/Linuxgeneric | 2.6.39 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.