CVE-2015-8615
The hvm_set_callback_via function in arch/x86/hvm/irq.c in Xen 4.6 does not limit the number of...
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).
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
Exploit likelihood
What each source reports
NVD Score used
5.0
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).
- Record
CVE-2015-8615- CVSS 3.0
- 5.0 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L - CVSS 2.0
- 2.1 Low
AV:L/AC:L/Au:N/C:N/I:N/A:P - Weakness
- CWE-254
- Updated
- 2026-11-02
CVE List No score
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).
- Record
CVE-2015-8615- Updated
- 2026-11-02
EUVDEUVD-2015-8492 No score
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).
- Record
EUVD-2015-8492- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-5p4h-mjwj-j325
5.0
The hvm_set_callback_via function in arch/x86/hvm/irq.c in Xen 4.6 does not limit the number of...
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).
- Record
GHSA-5p4h-mjwj-j325- CVSS 3.0
- 5.0 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L - Updated
- 2026-11-02
OSV
5.0
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).
- Record
CVE-2015-8615- CVSS 3.0
- 5.0 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L - Updated
- 2026-11-02
OSVDEBIAN-CVE-2015-8615
5.0
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).
- Record
DEBIAN-CVE-2015-8615- CVSS 3.0
- 5.0 Medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L - Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10196-1 No score
xen-4.7.0_12-1.3 on GA media
These are all security issues fixed in the xen-4.7.0_12-1.3 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10196-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
xenDebian:12 |
before 4.8.0~rc3-1 | 4.8.0~rc3-1 |
xenDebian:13 |
before 4.8.0~rc3-1 | 4.8.0~rc3-1 |
xenDebian:14 |
before 4.8.0~rc3-1 | 4.8.0~rc3-1 |
xenDebian:7 From an advisory covering 19 CVEs |
before 4.1.6.1-1+deb7u1, plus listed versions 4.1.4-34.1.4-3+deb7u14.1.4-3+deb7u24.1.4-3+deb7u34.1.4-3+deb7u4 Show 6 moreShow less4.1.4-3+deb7u54.1.4-3+deb7u64.1.4-3+deb7u74.1.4-3+deb7u84.1.4-3+deb7u94.1.4-4 |
4.1.6.1-1+deb7u1 |
xenopenSUSE:Tumbleweed From an advisory covering 124 CVEs |
before 4.7.0_12-1.3 | 4.7.0_12-1.3 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2015-8615 is a medium vulnerability (CVSS 5.0) in Xen, published January 8, 2016. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.16%, the 67th percentile. Fixed in xen 4.8.0~rc3-1.
References
xenbits.xen.org/xsa/advisory-169.html
securityfocus.com/bid/79644
securitytracker.com/id/1034512
nvd.nist.gov/vuln/detail/CVE-2015-8615
github.com/advisories/GHSA-5p4h-mjwj-j325
security-tracker.debian.org/tracker/CVE-2015-8615
Show 124 moreShow less
suse.com/security/cve/CVE-2011-1898
suse.com/security/cve/CVE-2012-0029
suse.com/security/cve/CVE-2012-0217
suse.com/security/cve/CVE-2012-2625
suse.com/security/cve/CVE-2012-3432
suse.com/security/cve/CVE-2012-3433
suse.com/security/cve/CVE-2012-4411
suse.com/security/cve/CVE-2012-4535
suse.com/security/cve/CVE-2012-4536
suse.com/security/cve/CVE-2012-4537
suse.com/security/cve/CVE-2012-4538
suse.com/security/cve/CVE-2012-4539
suse.com/security/cve/CVE-2012-4544
suse.com/security/cve/CVE-2012-5510
suse.com/security/cve/CVE-2012-5511
suse.com/security/cve/CVE-2012-5513
suse.com/security/cve/CVE-2012-5514
suse.com/security/cve/CVE-2012-5515
suse.com/security/cve/CVE-2012-5525
suse.com/security/cve/CVE-2012-5634
suse.com/security/cve/CVE-2012-6075
suse.com/security/cve/CVE-2013-0151
suse.com/security/cve/CVE-2013-0152
suse.com/security/cve/CVE-2013-0153
suse.com/security/cve/CVE-2013-1442
suse.com/security/cve/CVE-2013-1917
suse.com/security/cve/CVE-2013-1918
suse.com/security/cve/CVE-2013-1919
suse.com/security/cve/CVE-2013-1922
suse.com/security/cve/CVE-2013-1952
suse.com/security/cve/CVE-2013-2007
suse.com/security/cve/CVE-2013-3495
suse.com/security/cve/CVE-2013-4355
suse.com/security/cve/CVE-2013-4356
suse.com/security/cve/CVE-2013-4361
suse.com/security/cve/CVE-2013-4375
suse.com/security/cve/CVE-2013-4416
suse.com/security/cve/CVE-2013-4494
suse.com/security/cve/CVE-2013-4533
suse.com/security/cve/CVE-2013-4534
suse.com/security/cve/CVE-2013-4537
suse.com/security/cve/CVE-2013-4538
suse.com/security/cve/CVE-2013-4539
suse.com/security/cve/CVE-2013-4540
suse.com/security/cve/CVE-2013-4551
suse.com/security/cve/CVE-2013-4553
suse.com/security/cve/CVE-2013-4554
suse.com/security/cve/CVE-2014-0222
suse.com/security/cve/CVE-2014-3124
suse.com/security/cve/CVE-2014-3640
suse.com/security/cve/CVE-2014-3672
suse.com/security/cve/CVE-2014-5146
suse.com/security/cve/CVE-2014-5149
suse.com/security/cve/CVE-2014-6268
suse.com/security/cve/CVE-2014-7154
suse.com/security/cve/CVE-2014-7155
suse.com/security/cve/CVE-2014-7156
suse.com/security/cve/CVE-2014-7188
suse.com/security/cve/CVE-2014-7815
suse.com/security/cve/CVE-2015-1779
suse.com/security/cve/CVE-2015-3259
suse.com/security/cve/CVE-2015-3340
suse.com/security/cve/CVE-2015-3456
suse.com/security/cve/CVE-2015-4037
suse.com/security/cve/CVE-2015-4103
suse.com/security/cve/CVE-2015-4104
suse.com/security/cve/CVE-2015-4105
suse.com/security/cve/CVE-2015-4106
suse.com/security/cve/CVE-2015-5154
suse.com/security/cve/CVE-2015-5239
suse.com/security/cve/CVE-2015-5278
suse.com/security/cve/CVE-2015-5307
suse.com/security/cve/CVE-2015-6815
suse.com/security/cve/CVE-2015-6855
suse.com/security/cve/CVE-2015-7311
suse.com/security/cve/CVE-2015-7504
suse.com/security/cve/CVE-2015-7512
suse.com/security/cve/CVE-2015-7549
suse.com/security/cve/CVE-2015-7835
suse.com/security/cve/CVE-2015-7969
suse.com/security/cve/CVE-2015-7970
suse.com/security/cve/CVE-2015-7971
suse.com/security/cve/CVE-2015-7972
suse.com/security/cve/CVE-2015-8104
suse.com/security/cve/CVE-2015-8339
suse.com/security/cve/CVE-2015-8340
suse.com/security/cve/CVE-2015-8341
suse.com/security/cve/CVE-2015-8345
suse.com/security/cve/CVE-2015-8504
suse.com/security/cve/CVE-2015-8550
suse.com/security/cve/CVE-2015-8554
suse.com/security/cve/CVE-2015-8555
suse.com/security/cve/CVE-2015-8558
suse.com/security/cve/CVE-2015-8567
suse.com/security/cve/CVE-2015-8568
suse.com/security/cve/CVE-2015-8613
suse.com/security/cve/CVE-2015-8615
suse.com/security/cve/CVE-2015-8619
suse.com/security/cve/CVE-2015-8743
suse.com/security/cve/CVE-2015-8744
suse.com/security/cve/CVE-2015-8745
suse.com/security/cve/CVE-2016-1568
suse.com/security/cve/CVE-2016-1570
suse.com/security/cve/CVE-2016-1571
suse.com/security/cve/CVE-2016-1714
suse.com/security/cve/CVE-2016-1922
suse.com/security/cve/CVE-2016-1981
suse.com/security/cve/CVE-2016-2198
suse.com/security/cve/CVE-2016-2270
suse.com/security/cve/CVE-2016-2271
suse.com/security/cve/CVE-2016-2391
suse.com/security/cve/CVE-2016-2392
suse.com/security/cve/CVE-2016-2538
suse.com/security/cve/CVE-2016-2841
suse.com/security/cve/CVE-2016-4439
suse.com/security/cve/CVE-2016-4441
suse.com/security/cve/CVE-2016-5238
suse.com/security/cve/CVE-2016-5338
suse.com/security/cve/CVE-2016-6258
suse.com/security/cve/CVE-2016-6259
suse.com/security/cve/CVE-2016-6351
suse.com/security/cve/CVE-2016-7092
suse.com/security/cve/CVE-2016-7093
suse.com/security/cve/CVE-2016-7094