CVE-2026-23553: x86: incomplete IBPB for vCPU isolation
Noroxi assessment
Priority: Monitor (action score 11/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.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: xen (Alpine:v3.20) 4.18.5-r4; xen (Alpine:v3.21) 4.19.4-r1; xen (Alpine:v3.22) 4.20.2-r1.
Low priority for now. Upgrade to xen (Alpine:v3.20) 4.18.5-r4; xen (Alpine:v3.21) 4.19.4-r1; xen (Alpine:v3.22) 4.20.2-r1 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
In the context switch logic Xen attempts to skip an IBPB in the case of a vCPU returning to a CPU on which it was the previous vCPU to run. While safe for Xen's isolation between vCPUs, this prevents the guest kernel correctly isolating between tasks. Consider: 1) vCPU runs on CPU A, running task 1. 2) vCPU moves to CPU B, idle gets scheduled on A. Xen skips IBPB. 3) On CPU B, guest kernel switches from task 1 to 2, issuing IBPB. 4) vCPU moves back to CPU A. Xen skips IBPB again. Now, task 2 is running on CPU A with task 1's training still in the BTB.
- Published
- Jan 28, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-665
Report tools
Action score
11
Low priority for now.
- CVSS
- 11 / 40 · 2.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
- consult Xen advisory XSA-479unknown
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xen xen4.6.0 and later
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.20 | xen | from 4.6.0 · before 4.18.5-r4 | 4.18.5-r4 |
| Alpine:v3.21 | xen | from 4.6.0 · before 4.19.4-r1 | 4.19.4-r1 |
| Alpine:v3.22 | xen | from 4.6.0 · before 4.20.2-r1 | 4.20.2-r1 |
| Alpine:v3.24 | xen | from 4.6.0 · before 4.21.0-r2 | 4.21.0-r2 |
| Debian:12 | xen | before 4.17.7-0+deb12u1 | 4.17.7-0+deb12u1 |
| Debian:13 | xen | before 4.20.2+37-g61ff35323e-0+deb13u1 | 4.20.2+37-g61ff35323e-0+deb13u1 |
| Debian:14 | xen | before 4.20.2+37-g61ff35323e-1 | 4.20.2+37-g61ff35323e-1 |
| openSUSE:Leap 15.6 | xen | before 4.18.5_10-150600.3.37.1 | 4.18.5_10-150600.3.37.1 |
| openSUSE:Tumbleweed | xen | before 4.21.0_04-1.1 | 4.21.0_04-1.1 |
| SUSE:Linux Enterprise Micro 5.2 | xen | before 4.14.6_28-150300.3.94.1 | 4.14.6_28-150300.3.94.1 |
| SUSE:Linux Enterprise Micro 5.3 | xen | before 4.16.7_06-150400.4.78.1 | 4.16.7_06-150400.4.78.1 |
| SUSE:Linux Enterprise Micro 5.5 | xen | before 4.17.6_04-150500.3.59.1 | 4.17.6_04-150500.3.59.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | xen | before 4.20.2_04-150700.3.22.1 | 4.20.2_04-150700.3.22.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | xen | before 4.20.2_06-150700.3.25.1 | 4.20.2_06-150700.3.25.1 |
| SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | xen | before 4.12.4_64-3.137.1 | 4.12.4_64-3.137.1 |
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-2025-58149Oct 31, 2025 · Incorrect removal of permissions on PCI device unplug30Monitor
- ← EarlierCVE-2025-58150Jan 28, 2026 · x86: buffer overrun with shadow paging + tracing35Monitor
- Later →CVE-2026-23554Mar 23, 2026 · Use after free of paging structures in EPT31Monitor
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.18.5-r4 · Alpine:v3.20 | Package registry (OSV) |
| debian:xen | 4.17.7-0+deb12u1 · Debian:12 | Package registry (OSV) |
| debian:xen | 4.20.2+37-g61ff35323e-0+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:xen | 4.18.5_10-150600.3.37.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:xen | 4.14.6_28-150300.3.94.1 · SUSE:Linux Enterprise Micro 5.2 | 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.
- David KaplanAMD.finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-62433181 days apartcorrect buffer checks for DM_OP hypercalls29Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-665 · Improper InitializationCVSS vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.