Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2016-3159: The fpu_fxrstor function in arch/x86/i387.c in Xen 4.x does not properly handle writes to the hardware FSW.ES bit when running on AMD64…

LowCVSS 3.8 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 15/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.39% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: xen (Debian:12) 4.8.0~rc3-1; xen (Debian:7) 4.1.6.lts1-1; xen (Debian:8) 4.4.1-9+deb8u5.

Low priority for now. Upgrade to xen (Debian:12) 4.8.0~rc3-1; xen (Debian:7) 4.1.6.lts1-1; xen (Debian:8) 4.4.1-9+deb8u5 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

The fpu_fxrstor function in arch/x86/i387.c in Xen 4.x does not properly handle writes to the hardware FSW.ES bit when running on AMD64 processors, which allows local guest OS users to obtain sensitive register content information from another guest by leveraging pending exception and mask bits. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-2076.

Published
Apr 13, 2016
Updated
Jun 16, 2026
EPSS
0.3% · 34th percentile

Report tools

JSON

Action score

15

Monitor

Low priority for now.

CVSS
15 / 40 · 3.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

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-2016-3159

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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.

VendorProduct
xenxen
oraclevm server
fedoraprojectfedora
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux8.0
  • fedoraproject fedora22
  • fedoraproject fedora23
  • oracle vm server3.3
  • oracle vm server3.4
  • xen xen4.5.0 and later · up to 4.5.3 inclusive
  • xen xen4.6.0 and later · up to 4.6.1 inclusive
  • xen xen4.4.0 and later · up to 4.4.4 inclusive
  • xen xen4.3.0 and later · up to 4.3.4 inclusive

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12xenbefore 4.8.0~rc3-14.8.0~rc3-1
Debian:7xenbefore 4.1.6.lts1-14.1.6.lts1-1
Debian:8xenbefore 4.4.1-9+deb8u54.4.1-9+deb8u5
SUSE:Linux Enterprise Desktop 12 SP1xenbefore 4.5.3_08-17.14.5.3_08-17.1
SUSE:Linux Enterprise Server 11 SP2-LTSSxenbefore 4.1.6_08-29.14.1.6_08-29.1
SUSE:Linux Enterprise Server for SAP Applications 12xenbefore 4.4.4_04-22.22.24.4.4_04-22.22.2
SUSE:Linux Enterprise Software Development Kit 11 SP4xenbefore 4.4.4_07-37.14.4.4_07-37.1
SUSE:OpenStack Cloud 5xenbefore 4.2.5_21-27.14.2.5_21-27.1

Same product

xen: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-10921The grant-table feature in Xen through 4.8.x does not ensure sufficient type counts for a GNTMAP_device_map and GNTMAP_host_map mapping…
    41Plan
  • CVE-2017-10920The grant-table feature in Xen through 4.8.x mishandles a GNTMAP_device_map and GNTMAP_host_map mapping, when followed by only a…
    41Plan
  • CVE-2017-10918Xen through 4.8.x does not validate memory allocations during certain P2M operations, which allows guest OS users to obtain privileged host…
    41Plan

Published before and after this one in the same product

  • ← EarlierCVE-2015-8555Apr 13, 2016 · Xen 4.6.x, 4.5.x, 4.4.x, 4.3.x, and earlier do not initialize x86 FPU stack and XMM registers when XSAVE/XRSTOR are not used to manage…
    35Monitor
  • ← EarlierCVE-2016-3158Apr 13, 2016 · The xrstor function in arch/x86/xstate.c in Xen 4.x does not properly handle writes to the hardware FSW.ES bit when running on AMD64…
    15Monitor
  • Later →CVE-2015-8550Apr 14, 2016 · Xen, when used on a system providing PV backends, allows local guest OS administrators to cause a denial of service (host OS crash) or gain…
    32Monitor

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
debian:xen4.8.0~rc3-1 · Debian:12Package registry (OSV)
suse:xen4.5.3_08-17.1 · SUSE:Linux Enterprise Desktop 12 SP1Package 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.

Patch and commit links

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

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

References

All records