CVE-2021-28687: HVM soft-reset crashes toolstack libxl requires all data structures passed across its public interface to be initialized before use and…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: xen (Alpine:v3.11) 4.13.3-r0; xen (Alpine:v3.14) 4.15.0-r0; xen (Debian:12) 4.14.2+25-gb6a8c4f72d-1.
Low priority for now. Upgrade to xen (Alpine:v3.11) 4.13.3-r0; xen (Alpine:v3.14) 4.15.0-r0; xen (Debian:12) 4.14.2+25-gb6a8c4f72d-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
HVM soft-reset crashes toolstack libxl requires all data structures passed across its public interface to be initialized before use and disposed of afterwards by calling a specific set of functions. Many internal data structures also require this initialize / dispose discipline, but not all of them. When the "soft reset" feature was implemented, the libxl__domain_suspend_state structure didn't require any initialization or disposal. At some point later, an initialization function was introduced for the structure; but the "soft reset" path wasn't refactored to call the initialization function. When a guest nwo initiates a "soft reboot", uninitialized data structure leads to an assert() when later code finds the structure in an unexpected state. The effect of this is to crash the process monitoring the guest. How this affects the system depends on the structure of the toolstack. For xl, this will have no security-relevant effect: every VM has its own independent monitoring process, which contains no state. The domain in question will hang in a crashed state, but can be destroyed by `xl destroy` just like any other non-cooperating domain. For daemon-based toolstacks linked against libxl, such as libvirt, this will crash the toolstack, losing the state of any in-progress operations (localized DoS), and preventing further administrator operations unless the daemon is configured to restart automatically (system-wide DoS). If crashes "leak" resources, then repeated crashes could use up resources, also causing a system-wide DoS.
- Published
- Jun 11, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 24th percentile
- CWE
- CWE-909
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xen | xen | cpe:2.3:o:xen:xen |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (XEN). Independent of NVD's CPE analysis and usually ahead of it.
Xen xen
- xen-unstable, 4.14.xaffected
- unspecified and later · before 4.12unknown
- 4.12.x and later · before unspecifiedaffected
- next of 4.13.x and later · before unspecifiednot affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xen xen4.12 and later · up to 4.15.0 inclusive
- xen xen4.15.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.11 | xen | from 4.12 · before 4.13.3-r0 | 4.13.3-r0 |
| Alpine:v3.14 | xen | from 4.12 · before 4.15.0-r0 | 4.15.0-r0 |
| Debian:12 | xen | before 4.14.2+25-gb6a8c4f72d-1 | 4.14.2+25-gb6a8c4f72d-1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | xen | before 4.12.4_08-3.43.3 | 4.12.4_08-3.43.3 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | xen | before 4.13.2_08-3.25.3 | 4.13.2_08-3.25.3 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | before 4.12.4_09-3.39.3 | 4.12.4_09-3.39.3 |
Same product
xen: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-10921The grant-table feature in Xen through 4.8.x does not ensure sufficient type counts for a GNTMAP_device_map and GNTMAP_host_map mapping…41Plan
- CVE-2017-10920The grant-table feature in Xen through 4.8.x mishandles a GNTMAP_device_map and GNTMAP_host_map mapping, when followed by only a…41Plan
- CVE-2017-10918Xen through 4.8.x does not validate memory allocations during certain P2M operations, which allows guest OS users to obtain privileged host…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-26313Jun 9, 2021 · AMD Speculative Code Store Bypass22Monitor
- ← EarlierCVE-2021-26314Jun 9, 2021 · AMD Speculative execution with Floating-Point Value Injection22Monitor
- Later →CVE-2021-28689Jun 11, 2021 · x86: Speculative vulnerabilities with bare (non-shim) 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1.22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:xen | 4.13.3-r0 · Alpine:v3.11 | Package registry (OSV) |
| debian:xen | 4.14.2+25-gb6a8c4f72d-1 · Debian:12 | Package registry (OSV) |
| suse:xen | 4.12.4_09-3.39.3 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-909 · Missing Initialization of ResourceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.