CVE-2015-0268 json
The vgic_v2_to_sgi function in arch/arm/vgic-v2.c in Xen 4.5.x, when running on ARM hardware with general interrupt controller (GIC) versio…
published 11y ago modified 4mo ago also EUVD-2015-0284
- cvss
- 4.9
- 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 36%
- public exploits
- 0
- none known
Summary
The vgic_v2_to_sgi function in arch/arm/vgic-v2.c in Xen 4.5.x, when running on ARM hardware with general interrupt controller (GIC) version 2, allows local guest users to cause a denial of service (host crash) by writing an invalid value to the GICD.SGIR register.
Is CVE-2015-0268 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 FencerVendor 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-0268 updated cvss 4.9
xen: GICD_SGIR is not properly emulated on ARM architecture (XSA-117)
-
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
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.9 | AV:L/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
xenbits.xen.org
/xsa/advisory-117.html
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/100868
vdb-entry
-
securitytracker.com
/id/1031746
vdb-entry
-
securityfocus.com
/bid/72591
vdb-entry
Sources
- CVE List CVE-2015-0268
- NVD CVE-2015-0268
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.