xen: hypervisor memory corruption due to x86 emulator flaw (xsa123)
Published Mar 12, 2015
7.2
HIGHCVSS 2.0
EPSS 0.55%
Description
The x86 emulator in Xen 3.2.x through 4.5.x does not properly ignore segment overrides for instructions with register operands, which allows local guest users to obtain sensitive information, cause a denial of service (memory corruption), or possibly execute arbitrary code via unspecified vectors.
Affected products
No data.
Configuration 1
- 20
- 21
- 22
Configuration 2
- 7.0
Configuration 3
- 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.1
- 4.2.0
- 4.2.1
- 4.2.2
- 4.2.3
- 4.3.0
- 4.3.1
- 4.4.0
- 4.4.0
- 4.4.1
- 4.5.0
No data.
Red Hat Enterprise Linux 5
kernel-0:2.6.18-409.el5
Fixed · RHSA-2016:0450
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | kernel-0:2.6.18-409.el5 | Fixed | RHSA-2016:0450 |
No package ranges for this CVE.
Remediation
Red Hat statement
This issue does affect the Xen hypervisor packages as shipped with Red Hat Enterprise Linux 5. Future Xen hypervisor packages updates might address this issue.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
No CVSS v3.0 score for this CVE.
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 (9 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 0.55% (0.00548) | 43.85th | v5 (v2026.06.15) |
| Jun 15, 2026 | 0.57% (0.00570) | 42.48th | v5 (v2026.06.15) |
| Mar 17, 2025 | 0.28% (0.00284) | 49.71th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.09% (0.00086) | 38.23th | v3 (v2023.03.01) |
| Jun 26, 2024 | 0.09% (0.00086) | 36.79th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.09% (0.00086) | 34.76th | v3 (v2023.03.01) |
| Mar 6, 2023 | 2.17% (0.02172) | 80.27th | v2 (v2022.01.01) |
| Apr 1, 2022 | 2.17% (0.02172) | 78.34th | v2 (v2022.01.01) |
| Feb 4, 2022 | 2.17% (0.02172) | 57.15th | v2 (v2022.01.01) |
References (18)
- http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10761 x_refsource_CONFIRM
- http://lists.fedoraproject.org/pipermail/package-announce/2015-March/152483.html vendor-advisoryx_refsource_FEDORAThird Party Advisory
- http://lists.fedoraproject.org/pipermail/package-announce/2015-March/152588.html vendor-advisoryx_refsource_FEDORAThird Party Advisory
- http://lists.fedoraproject.org/pipermail/package-announce/2015-March/152776.html vendor-advisoryx_refsource_FEDORAThird Party Advisory
- http://lists.opensuse.org/opensuse-security-announce/2015-04/msg00014.html vendor-advisoryx_refsource_SUSE
- http://support.citrix.com/article/CTX200484 x_refsource_CONFIRM
- http://www.debian.org/security/2015/dsa-3181 vendor-advisoryx_refsource_DEBIANThird Party Advisory
- http://www.oracle.com/technetwork/topics/security/linuxbulletinjan2016-2867209.html x_refsource_CONFIRM
- http://www.securityfocus.com/bid/73015 vdb-entryx_refsource_BID
- http://www.securitytracker.com/id/1031806 vdb-entryx_refsource_SECTRACKThird Party AdvisoryVDB Entry
- http://www.securitytracker.com/id/1031903 vdb-entryx_refsource_SECTRACKThird Party AdvisoryVDB Entry
- http://www1.huawei.com/en/security/psirt/security-bulletins/security-advisories/hw-423503.htm x_refsource_CONFIRM
- http://xenbits.xen.org/xsa/advisory-123.html x_refsource_CONFIRMPatchVendor Advisory
- https://access.redhat.com/security/cve/CVE-2015-2151 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1196274 Issue Tracking
- https://nvd.nist.gov/vuln/detail/CVE-2015-2151
- https://security.gentoo.org/glsa/201604-03 vendor-advisoryx_refsource_GENTOO
- https://www.cve.org/CVERecord?id=CVE-2015-2151
Change history (0)
No recorded changes yet.