CVE-2026-43265
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 6.1.167
- Linux Kernel < 6.6.130
- Linux Kernel < 6.12.77
- Linux Kernel < 6.18.17
- Linux Kernel < 6.19.6
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43265.md and follow it. Check whether this project is affected by CVE-2026-43265. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1c957773063ed3264953597e32990a748381caf6
- https://git.kernel.org/stable/c/1e88b5f854bdb469424132e0bb44793ad7a7c20a
- https://git.kernel.org/stable/c/2657439265d34a911886b916ba8be97ecc117d51
- https://git.kernel.org/stable/c/78265cd066d73a5cb41c088fcae4a2515e480d97
- https://git.kernel.org/stable/c/ead63640d4e72e6f6d464f4e31f7fecb79af8869
- https://git.kernel.org/stable/c/ec3be7dc9391085a2d96700e159d66d1328b7ff6
References
- https://git.kernel.org/stable/c/1c957773063ed3264953597e32990a748381caf6
- https://git.kernel.org/stable/c/1e88b5f854bdb469424132e0bb44793ad7a7c20a
- https://git.kernel.org/stable/c/2657439265d34a911886b916ba8be97ecc117d51
- https://git.kernel.org/stable/c/78265cd066d73a5cb41c088fcae4a2515e480d97
- https://git.kernel.org/stable/c/ead63640d4e72e6f6d464f4e31f7fecb79af8869
- https://git.kernel.org/stable/c/ec3be7dc9391085a2d96700e159d66d1328b7ff6