Skip to content
Fencer Intel
medium 4.7

CVE-2013-3495 json

The Intel VT-d Interrupt Remapping engine in Xen 3.3.x through 4.3.x allows local guests to cause a denial of service (kernel panic) via a…

published 13y ago modified 4mo ago also EUVD-2013-3430

cvss
4.7
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 33%
public exploits
0
none known

Summary

The Intel VT-d Interrupt Remapping engine in Xen 3.3.x through 4.3.x allows local guests to cause a denial of service (kernel panic) via a malformed Message Signaled Interrupt (MSI) from a PCI device that is bus mastering capable that triggers a System Error Reporting (SERR) Non-Maskable Interrupt (NMI).

Patch / fix

  • xen Debian 14, Debian 13, Debian 12 4.4.1-3

debian advisories DEBIAN-CVE-2013-3495

  • xen openSUSE Tumbleweed 4.7.0_12-1.3

opensuse advisories openSUSE-SU-2024:10196-1

Is CVE-2013-3495 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-2013-3495 updated cvss 4.3

hw: virt: Intel VT-d Interrupt Remapping engines can be evaded by native NMI interrupts

  • Red Hat Enterprise Linux 5 kernel-xen
    affected: no fix available

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.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

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.