CVE-2016-4962

The libxl device-handling in Xen 4.6.x and earlier allows local OS guest administrators to cause a denial of service (resource consumption or management facility confusion) or gain host OS privileges by manipulating information in guest controlled areas of xenstore.

Published: 2016-06-07 Last update: 2026-05-06 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-4962 is rated Low Risk (38.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.40%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-4962

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.14% 0.40% +0.26%
2 2025-03-30 0.31% 0.14% -0.17%
3 2025-03-29 — 0.31% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-4962

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:L/AC:L/Au:S/C:C/I:C/A:C Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 3.1 10.0 [email protected]

Weakness enumeration for CVE-2016-4962

OS Trackers for CVE-2016-4962

vendor priority summary link
debian not yet assigned CVE-2016-4962 not yet assigned priority: Debian including 1 source packages (xen), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-4962
redhat medium — https://access.redhat.com/security/cve/CVE-2016-4962
suse medium CVE-2016-4962 severity moderate: SUSE including 25 source package names (xen, xen-4.4.4_04-22.22.2, …), 53 product×package rows across 12 product lines (SUSE Linux Enterprise Desktop 12 SP1, SUSE Linux Enterprise Server 11 SP1 for Teradata, … (12 product lines)): Fixed 50, Known Not Affected 3. https://www.suse.com/security/cve/CVE-2016-4962/
ubuntu medium CVE-2016-4962 medium priority: Ubuntu including 1 source packages (xen), 5 status rows across 5 suites (precise, trusty, upstream, wily, xenial): released 3, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2016-4962

Affected software / configurations for CVE-2016-4962

Vendor Product Version Raw CPE
oracle vm_server 3.3 cpe:2.3:o:oracle:vm_server:3.3:*:*:*:*:*:*:*
oracle vm_server 3.4 cpe:2.3:o:oracle:vm_server:3.4:*:*:*:*:*:*:*
xen xen 4.3.0 cpe:2.3:o:xen:xen:4.3.0:*:*:*:*:*:*:*
xen xen 4.3.1 cpe:2.3:o:xen:xen:4.3.1:*:*:*:*:*:*:*
xen xen 4.3.2 cpe:2.3:o:xen:xen:4.3.2:*:*:*:*:*:*:*
xen xen 4.3.3 cpe:2.3:o:xen:xen:4.3.3:*:*:*:*:*:*:*
xen xen 4.3.4 cpe:2.3:o:xen:xen:4.3.4:*:*:*:*:*:*:*
xen xen 4.4.0 cpe:2.3:o:xen:xen:4.4.0:*:*:*:*:*:*:*
xen xen 4.4.0 cpe:2.3:o:xen:xen:4.4.0:rc1:*:*:*:*:*:*
xen xen 4.4.1 cpe:2.3:o:xen:xen:4.4.1:*:*:*:*:*:*:*
xen xen 4.4.2 cpe:2.3:o:xen:xen:4.4.2:*:*:*:*:*:*:*
xen xen 4.4.3 cpe:2.3:o:xen:xen:4.4.3:*:*:*:*:*:*:*
xen xen 4.4.4 cpe:2.3:o:xen:xen:4.4.4:*:*:*:*:*:*:*
xen xen 4.5.0 cpe:2.3:o:xen:xen:4.5.0:*:*:*:*:*:*:*
xen xen 4.5.1 cpe:2.3:o:xen:xen:4.5.1:*:*:*:*:*:*:*
xen xen 4.5.2 cpe:2.3:o:xen:xen:4.5.2:*:*:*:*:*:*:*
xen xen 4.5.3 cpe:2.3:o:xen:xen:4.5.3:*:*:*:*:*:*:*
xen xen 4.6.0 cpe:2.3:o:xen:xen:4.6.0:*:*:*:*:*:*:*
xen xen 4.6.1 cpe:2.3:o:xen:xen:4.6.1:*:*:*:*:*:*:*

References for CVE-2016-4962

cvelogic Threat Intelligence