CVE-2026-43265KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block()
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() Ignore -EBUSY when checking nested events after exiting a blocking state while L2 is active, as exiting to userspace will generate a spurious userspace exit, usually with KVM_EXIT_UNKNOWN, and likely lead to the VM's demise. Continuing with the wakeup isn't perfect either, as *something* has gone sideways if a vCPU is awakened in L2 with an injected event (or worse, a nested run pending), but continuing on gives the VM a decent chance of surviving without any major side effects. As explained in the Fixes commits, it _should_ be impossible for a vCPU to be put into a blocking state with an already-injected event (exception, IRQ, or NMI). Unfortunately, userspace can stuff MP_STATE and/or injected events, and thus put the vCPU into what should be an impossible state. Don't bother trying to preserve the WARN, e.g. with an anti-syzkaller Kconfig, as WARNs can (hopefully) be added in paths where _KVM_ would be violating x86 architecture, e.g. by WARNing if KVM attempts to inject an exception or interrupt while the vCPU isn't running.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 26844fee6adee9b1557d2279b0506285de9ee82b – < 78265cd066d73a5cb41c088fcae4a2515e480d97
- affected 26844fee6adee9b1557d2279b0506285de9ee82b – < ec3be7dc9391085a2d96700e159d66d1328b7ff6
- affected 26844fee6adee9b1557d2279b0506285de9ee82b – < 2657439265d34a911886b916ba8be97ecc117d51
- affected 26844fee6adee9b1557d2279b0506285de9ee82b – < 1e88b5f854bdb469424132e0bb44793ad7a7c20a
- affected 26844fee6adee9b1557d2279b0506285de9ee82b – < 1c957773063ed3264953597e32990a748381caf6
- affected 26844fee6adee9b1557d2279b0506285de9ee82b – < ead63640d4e72e6f6d464f4e31f7fecb79af8869
- affected 6.1
- unaffected < 6.1
- unaffected 6.1.167 – ≤ 6.1.*
- unaffected 6.6.130 – ≤ 6.6.*
- unaffected 6.12.77 – ≤ 6.12.*
- unaffected 6.18.17 – ≤ 6.18.*
- unaffected 6.19.6 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/78265cd066d73a5cb41c088fcae4a2515e480d97 (opens in a new tab)
- https://git.kernel.org/stable/c/ec3be7dc9391085a2d96700e159d66d1328b7ff6 (opens in a new tab)
- https://git.kernel.org/stable/c/2657439265d34a911886b916ba8be97ecc117d51 (opens in a new tab)
- https://git.kernel.org/stable/c/1e88b5f854bdb469424132e0bb44793ad7a7c20a (opens in a new tab)
- https://git.kernel.org/stable/c/1c957773063ed3264953597e32990a748381caf6 (opens in a new tab)
- https://git.kernel.org/stable/c/ead63640d4e72e6f6d464f4e31f7fecb79af8869 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-27662 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43265)Record last updated .