Skip to content
Fencer Intel
medium 4.9

CVE-2015-4163 json

GNTTABOP_swap_grant_ref in Xen 4.2 through 4.5 does not check the grant table operation version, which allows local guest domains to cause…

published 11y ago modified 4mo ago also EUVD-2015-4187

cvss
4.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

GNTTABOP_swap_grant_ref in Xen 4.2 through 4.5 does not check the grant table operation version, which allows local guest domains to cause a denial of service (NULL pointer dereference) via a hypercall without a GNTTABOP_setup_table or GNTTABOP_set_version.

Patch / fix

  • xen Debian 14, Debian 13, Debian 12 4.6.0-1

debian advisories DEBIAN-CVE-2015-4163

  • xen Ubuntu 14.04 LTS 4.4.2-0ubuntu0.14.04.2

ubuntu advisories UBUNTU-CVE-2015-4163

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • xen SLES for SAP 12, SLES 12, SLED 12 +1 more 4.4.2_06-21.1

suse advisories SUSE-SU-2015:1042-1

Is CVE-2015-4163 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-4163 updated cvss 2.9

xen: GNTTABOP_swap_grant_ref operation misbehavior (xsa-134)

  • Red Hat Enterprise Linux 5 xen
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:N/I:N/A:C

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.