Skip to main content

Linux Kernel KVM EUVDEUVD-2026-59183

| CVE-2026-72284 HIGH
2026-08-15 Linux GHSA-4wpm-cf5q-x355
7.1
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.1 HIGH
AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
vuln.today AI
7.1 HIGH

Guest-local, no-privilege execution suffices to crash the host kernel across the VM boundary, justifying S:C and A:H with no C or I impact.

3.1 AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
SUSE
6.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 08:08 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.1 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 05:55 cve.org
HIGH 7.1
CVE Published
Aug 15, 2026 - 05:55 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

KVM: x86: Ignore pending PV EOI if the vCPU has since disabled PV EOIs

Ignore KVM's internal "service pending PV EOI" request if the vCPU has disabled PV EOIs since the request was made. Asserting that PV EOIs are enabled can fail if reading guest memory in pv_eoi_get_user() fails, i.e. if pv_eoi_test_and_clr_pending() bails early, *and* the vCPU also disables PV EOIs.

kernel BUG at arch/x86/kvm/lapic.c:3338! Oops: invalid opcode: 0000 [#1] SMP CPU: 4 UID: 1000 PID: 890 Comm: pv_eoi_test Not tainted 7.0.0-d585aa5894d8-vm #337 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:kvm_lapic_sync_from_vapic+0x12b/0x140 [kvm] Call Trace: <TASK> kvm_arch_vcpu_ioctl_run+0x1075/0x1c30 [kvm] kvm_vcpu_ioctl+0x2d5/0x980 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb5/0xb40 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK> Modules linked in: kvm_intel kvm irqbypass ---[ end trace 0000000000000000 ]---

AnalysisAI

Denial-of-service in the Linux kernel's KVM x86 subsystem allows a guest VM to crash the host hypervisor by exploiting a state inconsistency in PV EOI (paravirtual end-of-interrupt) handling. When a guest triggers a memory read failure in pv_eoi_get_user() while concurrently disabling PV EOI, KVM fires a fatal assertion in kvm_lapic_sync_from_vapic() at lapic.c:3338, producing a kernel BUG and crashing the host. This takes down all co-resident virtual machines. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but vendor-confirmed patches are available across multiple stable kernel branches.

Technical ContextAI

Paravirtual EOI (PV EOI) is a KVM performance optimization for x86 Local APIC emulation that allows guest VMs to acknowledge interrupts via a shared guest-host memory region, avoiding a full VM exit per EOI. The affected code path is in kvm_lapic_sync_from_vapic() within arch/x86/kvm/lapic.c. When a pending PV EOI service request is outstanding, KVM calls pv_eoi_test_and_clr_pending(), which internally calls pv_eoi_get_user() to read the guest-shared memory region. If that memory read fails and the function returns early, yet the vCPU subsequently disables PV EOI via its MSR, a subsequent assertion that PV EOI must still be enabled fires as a kernel BUG. The root cause is a TOCTOU-class logic error (closest to CWE-617, Reachable Assertion): the pending-service flag and the PV EOI enabled state are checked at different points without re-validation, allowing an inconsistent intermediate state to reach a hard assertion. CPE data (cpe:2.3:a:linux:linux:*) confirms this affects the Linux kernel broadly. PV EOI support was introduced in Linux 3.6, which defines the earliest affected version. The crash backtrace names the KVM Intel module (kvm_intel, kvm) and the test reproducer pv_eoi_test run by a non-privileged UID.

RemediationAI

Apply vendor-released patches for your kernel branch: upgrade to Linux 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, or 7.2-rc4 or later, sourced from https://git.kernel.org/stable/. Linux distribution vendors (Red Hat, Ubuntu, SUSE, Debian) are expected to carry these upstream stable fixes in their respective kernel update channels - consult your distribution's security advisory tracker for package-level versions. If patching is not immediately feasible, disable PV EOI in KVM guests by configuring the guest CPU without the kvm-pv-eoi CPUID feature (e.g., via <feature policy='disable' name='kvm-pv-eoi'/> in libvirt XML, or by passing -cpu ...,kvm-pv-eoi=off to QEMU). This prevents the vulnerable code path from ever being entered, at the cost of slightly increased interrupt latency due to additional VM exits for each EOI; this trade-off is generally acceptable as a short-term mitigation. Restricting which users can create or control KVM guest VMs reduces the attack surface but does not eliminate the vulnerability for already-running guests with PV EOI enabled.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

EUVD-2026-59183 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy