Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72138: xen/gntdev: fix error handling in ioctl

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454, 18a693733f7ad004e1ab0466693121ca70cd95dd, 1dd9cb98fe228e017fff9efb33862ff38c741b65.

Low priority for now. Upgrade to Linux Linux 16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454, 18a693733f7ad004e1ab0466693121ca70cd95dd, 1dd9cb98fe228e017fff9efb33862ff38c741b65 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72138

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.39affected
    • 68b025c813c2eb41ff25628e3d4952d5185eb1a4 and later · before 52dc40ef0cfee6ae89b7524967e73f0ba37906d7affected · git
    • 68b025c813c2eb41ff25628e3d4952d5185eb1a4 and later · before 1dd9cb98fe228e017fff9efb33862ff38c741b65affected · git
    • 68b025c813c2eb41ff25628e3d4952d5185eb1a4 and later · before 6df926130aee6cab9b5d2e5b7862e49ccac348dcaffected · git
    • 68b025c813c2eb41ff25628e3d4952d5185eb1a4 and later · before 311011f8cc206c5af2877b03e3f627ee1b8fe024affected · git
    • 68b025c813c2eb41ff25628e3d4952d5185eb1a4 and later · before 18a693733f7ad004e1ab0466693121ca70cd95ddaffected · git
    • 68b025c813c2eb41ff25628e3d4952d5185eb1a4 and later · before 16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454affected · git
    • 68b025c813c2eb41ff25628e3d4952d5185eb1a4 and later · before 6883269a323609f68f6faa903f8f8ff3d191cec8affected · git
    • 68b025c813c2eb41ff25628e3d4952d5185eb1a4 and later · before 45ca1afe2fd14c04e37227e79d3f8455831d8408affected · git
    • before 2.6.39not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72134Aug 15, 2026 · spi: imx: reconfigure for PIO when DMA cannot be started
    31Monitor
  • ← EarlierCVE-2026-72137Aug 15, 2026 · xfrm: nat_keepalive: avoid double free on send error
    39Monitor
  • Later →CVE-2026-72139Aug 15, 2026 · tcp: defer md5sig_info kfree past RCU grace period in tcp_connect
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux16d3ccdabb8dee9be2cdcd6d3f9a125572ec0454Vendor (CNA)
Linux Linux18a693733f7ad004e1ab0466693121ca70cd95ddVendor (CNA)
Linux Linux1dd9cb98fe228e017fff9efb33862ff38c741b65Vendor (CNA)
Linux Linux311011f8cc206c5af2877b03e3f627ee1b8fe024Vendor (CNA)
Linux Linux45ca1afe2fd14c04e37227e79d3f8455831d8408Vendor (CNA)
Linux Linux52dc40ef0cfee6ae89b7524967e73f0ba37906d7Vendor (CNA)
Linux Linux6883269a323609f68f6faa903f8f8ff3d191cec8Vendor (CNA)
Linux Linux6df926130aee6cab9b5d2e5b7862e49ccac348dcVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records