CVE-2026-80895
Received Received - Intake

Race Condition in Linux Kernel MSHV Hypervisor

Vulnerability report for CVE-2026-80895, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-04

Last updated on: 2026-09-04

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: mshv: Order pt_vp_array publish against irqfd assertion path mshv_partition_ioctl_create_vp() initialises a VP struct (allocations, mutex_init, init_waitqueue_head, page mappings) and then publishes the pointer into partition->pt_vp_array. Several ISR paths read this array locklessly: the intercept ISR, the two scheduler ISRs, and mshv_try_assert_irq_fast() on the irqfd fast path. Of these, only mshv_try_assert_irq_fast() can structurally race the publish. It runs from an eventfd waker without holding pt_mutex, and MSHV_IRQFD does not require the target lapic_apic_id (== vp_index) to refer to an existing VP at registration time. A user can therefore register an irqfd targeting a yet-to-be-created VP, then trigger mshv_try_assert_irq_fast() concurrently with MSHV_CREATE_VP for the same index. On weakly-ordered architectures the reader can observe a non-NULL pointer in pt_vp_array before the initialising stores to the VP struct become visible, leading to use of partially-initialised fields (e.g. vp_register_page). The other ISR readers cannot reach this race: the hypervisor will not generate intercept or scheduler messages for a VP that has never been told to run, and the user can only call MSHV_RUN_VP on the VP fd returned by MSHV_CREATE_VP, which by construction is returned after the publish. Leave those readers as plain loads. Use smp_store_release() in mshv_partition_ioctl_create_vp() to publish the pointer, and pair it with smp_load_acquire() in mshv_try_assert_irq_fast(). On x86 these compile to plain accesses under TSO; on ARM64 they emit one-instruction acquire/release barriers, acceptable on this fast path. The destroy-side path (destroy_partition() clearing pt_vp_array[i] to NULL after kfree(vp)) has a separate ordering and lifetime concern that is out of scope here.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-04
Last Modified
2026-09-04
Generated
2026-09-05
AI Q&A
2026-09-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a race condition in the Linux kernel's Microsoft Hypervisor (MSHV) component. It occurs when a virtual processor (VP) is created and published in an array while another process tries to use it before initialization completes. On weakly-ordered architectures, the reader may see a partially initialized VP struct, leading to potential memory corruption or crashes.

Detection Guidance

This vulnerability is specific to the Linux kernel's mshv (Microsoft Hypervisor) subsystem and requires kernel-level inspection. Detection involves checking kernel logs for related errors or verifying if your kernel version includes the fix. Commands like 'dmesg | grep mshv' or 'uname -a' to check kernel version may help. However, no direct detection commands are provided in the context.

Impact Analysis

This vulnerability could allow a local attacker to cause a denial of service (kernel crash) or potentially execute arbitrary code in the kernel context. It requires the attacker to have the ability to create and manage virtual machines or devices using MSHV.

Mitigation Strategies

Apply the latest kernel patches or updates that include the fix for CVE-2026-80895. The vulnerability is resolved by using smp_store_release() and smp_load_acquire() in the mshv_partition_ioctl_create_vp() function. Ensure your system is running a patched kernel version.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80895. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart