xen: Linux pciback missing sanity checks leading to crash (XSA-157)
Published Apr 13, 2016
4.4
MEDIUMCVSS 3.0
EPSS 0.45%
Description
The PCI backend driver in Xen, when running on an x86 system and using Linux 3.1.x through 4.3.x as the driver domain, allows local guest administrators to generate a continuous stream of WARN messages and cause a denial of service (disk consumption) by leveraging a system with access to a passed-through MSI or MSI-X capable physical PCI device and XEN_PCI_OP_enable_msi operations, aka "Linux pciback missing sanity checks."
Affected products
No data.
Configuration 1
- 3.1.3
- 3.1.4
- 3.2.0
- 3.2.1
- 3.2.2
- 3.2.3
- 3.3.0
- 3.3.1
- 3.3.2
- 3.4.0
- 3.4.1
- 3.4.2
- 3.4.3
- 3.4.4
- 4.0.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.0.4
- 4.1.0
- 4.1.1
- 4.1.2
- 4.1.3
- 4.1.4
- 4.1.5
- 4.1.6
- 4.1.6.1
- 4.2.0
- 4.2.1
- 4.2.2
- 4.2.3
- 4.2.4
- 4.2.5
- 4.3.0
- 4.3.1
- 4.3.2
- 4.3.3
- 4.3.4
Configuration 2
- 12.04
- 6.0
Configuration 3
No data.
Red Hat Enterprise Linux 5
kernel-xen
Will not fix
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | kernel-xen | Will not fix | n/a |
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
AV:L/AC:L/Au:S/C:N/I:N/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (12 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 0.45% (0.00446) | 36.47th | v5 (v2026.06.15) |
| Jun 15, 2026 | 0.45% (0.00446) | 35.30th | v5 (v2026.06.15) |
| Mar 30, 2025 | 0.27% (0.00274) | 47.94th | v4 (v2025.03.14) |
| Mar 29, 2025 | 2.97% (0.02968) | 77.47th | v4 (v2025.03.14) |
| Mar 17, 2025 | 0.27% (0.00274) | 48.82th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.08% (0.00076) | 34.56th | v3 (v2023.03.01) |
| Jun 12, 2024 | 0.08% (0.00076) | 32.51th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.08% (0.00076) | 30.50th | v3 (v2023.03.01) |
| Mar 6, 2023 | 1.28% (0.01282) | 68.34th | v2 (v2022.01.01) |
| Feb 22, 2023 | 1.28% (0.01282) | 68.05th | v2 (v2022.01.01) |
| Apr 1, 2022 | 1.28% (0.01282) | 65.91th | v2 (v2022.01.01) |
| Feb 4, 2022 | 1.28% (0.01282) | 41.72th | v2 (v2022.01.01) |
References (16)
- http://lists.opensuse.org/opensuse-security-announce/2016-03/msg00094.html vendor-advisoryx_refsource_SUSE
- http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00045.html vendor-advisoryx_refsource_SUSE
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00059.html vendor-advisoryx_refsource_SUSEThird Party Advisory
- http://lists.opensuse.org/opensuse-security-announce/2016-07/msg00005.html vendor-advisoryx_refsource_SUSEThird Party Advisory
- http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00000.html vendor-advisoryx_refsource_SUSEThird Party Advisory
- http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00044.html vendor-advisoryx_refsource_SUSE
- http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00055.html vendor-advisoryx_refsource_SUSE
- http://www.debian.org/security/2016/dsa-3434 vendor-advisoryx_refsource_DEBIAN
- http://www.securityfocus.com/bid/79546 vdb-entryx_refsource_BIDThird Party AdvisoryVDB Entry
- http://www.securitytracker.com/id/1034480 vdb-entryx_refsource_SECTRACKThird Party AdvisoryVDB Entry
- http://xenbits.xen.org/xsa/advisory-157.html x_refsource_CONFIRMVendor Advisory
- https://access.redhat.com/security/cve/CVE-2015-8552 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1289128 Issue Tracking
- https://nvd.nist.gov/vuln/detail/CVE-2015-8552
- https://security.gentoo.org/glsa/201604-03 vendor-advisoryx_refsource_GENTOO
- https://www.cve.org/CVERecord?id=CVE-2015-8552
Change history (0)
No recorded changes yet.