CVE-2026-99342 in Linuxinfo

Summary

by MITRE • 11/19/2026

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

KVM: x86/xen: Enforce 4-byte alignment of vcpu_info registration

Xen's map_guest_area() enforces that vcpu_info is aligned to sizeof(xen_ulong_t). KVM has no such check, allowing a guest to register vcpu_info at an arbitrary byte alignment.

Enforce unconditional 4-byte alignment regardless of the current shinfo mode. This is sufficient because subsequent commits ensure that all locked atomic operations on vcpu_info fields use at most 32-bit accesses. Return -ENXIO on failure, matching Xen's map_guest_area() behaviour for unaligned requests.

Originally observed in review of an unrelated patch: https://lore.kernel.org/all/[email protected]/

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/19/2026

The Linux kernel's KVM subsystem for x86 architecture contained a validation deficiency in the handling of Xen compatibility mode vcpu_info registrations, specifically within the map_guest_area logic. This vulnerability stems from an inconsistency between how the upstream Xen hypervisor and its KVM implementation manage guest memory mappings for virtual CPU information structures. In the native Xen environment, the map_guest_area function strictly enforces that the physical address provided by a guest domain for vcpu_info is aligned to sizeof(xen_ulong_t), which typically corresponds to 8 bytes on 64-bit systems but serves as a baseline for atomic operation safety. KVM failed to replicate this alignment check, allowing unprivileged guests to register their vcpu_info structures at arbitrary byte alignments that do not satisfy the requirements for safe memory access operations.

The technical root cause of this flaw lies in the lack of unconditional 4-byte alignment enforcement during the registration process. While subsequent kernel commits ensured that all locked atomic operations performed on vcpu_info fields utilize at most 32-bit accesses, these optimizations rely heavily on proper memory alignment to function correctly and avoid hardware-level exceptions or undefined behavior. By permitting misaligned addresses, KVM exposed a scenario where guest code could trigger unaligned memory access patterns within the host kernel context when interacting with these structures. This discrepancy represents an implementation error that deviates from established security best practices for handling shared data structures between virtual machines and hypervisors.

From an operational impact perspective, this vulnerability allows a malicious or buggy guest operating system to potentially cause instability in the KVM host environment. Although direct remote code execution is not explicitly detailed as a primary outcome of misalignment alone, such conditions can lead to kernel panics, denial of service through CPU exceptions, or unpredictable behavior depending on the underlying hardware architecture's tolerance for unaligned accesses. In some architectures, unaligned atomic operations may result in data corruption within the vcpu_info structure, potentially affecting scheduling decisions or interrupt handling mechanisms managed by KVM. The absence of proper validation creates a vector where guest actions can negatively impact host stability and security posture without requiring elevated privileges on the guest side.

This issue is categorized under CWE-20 Improper Input Validation, as it involves failing to adequately verify that input parameters meet required structural constraints before processing them within critical kernel subsystems. Furthermore, from an adversary behavior perspective, this aligns with ATT&CK technique T1498 Network Denial of Service, specifically the subcategory of resource exhaustion via logical errors or exceptions induced by malformed inputs. The vulnerability highlights the importance of maintaining parity between upstream hypervisor implementations and their virtualization counterparts to ensure consistent security boundaries across different execution environments.

To mitigate this risk, it is imperative that system administrators apply kernel updates provided by their respective distributions which include the patch enforcing unconditional 4-byte alignment for vcpu_info registration. This fix ensures that any attempt to register a misaligned address results in an immediate failure with return code -ENXIO, mirroring the behavior of Xen's map_guest_area function and preventing the guest from establishing invalid memory mappings. Organizations relying on KVM-based virtualization should verify their kernel versions against vendor security advisories and prioritize updates for systems running affected Linux kernels to close this validation gap and restore robust protection against potential denial-of-service attacks originating from untrusted guests.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00215

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!