CVE-2015-8615 json
The hvm_set_callback_via function in arch/x86/hvm/irq.c in Xen 4.6 does not limit the number of printk console messages when logging the ne…
published 2016-01-08 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-8492
- cvss
- 5.0
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
The hvm_set_callback_via function in arch/x86/hvm/irq.c in Xen 4.6 does not limit the number of printk console messages when logging the new callback method, which allows local HVM guest OS users to cause a denial of service via a large number of changes to the callback method (HVM_PARAM_CALLBACK_IRQ).
Patch / fix
- xen Debian 14, Debian 13, Debian 12 4.8.0~rc3-1
debian advisories DEBIAN-CVE-2015-8615
- xen openSUSE Tumbleweed 4.7.0_12-1.3
opensuse advisories openSUSE-SU-2024:10196-1
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-8615 updated cvss 4.0
xen: Unintentional logging upon guest changing callback method on x86
-
Red Hat Enterprise Linux 5 xennot 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
1.16% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.0 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-254 7PK - Security Features
References
-
xenbits.xen.org
/xsa/advisory-169.html
vendor-advisory
-
securityfocus.com
/bid/79644
vdb-entry
-
securitytracker.com
/id/1034512
vdb-entry
Sources
- CVE List CVE-2015-8615
- NVD CVE-2015-8615
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.