CVE-2025-38351

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush In KVM guests with Hyper-V hypercalls enabled, the hypercalls HVCALL_FLUSH_VIRTUAL_ADDRESS_LIST and HVCALL_FLUSH_VIRTUAL_ADDRESS_LIST_EX allow a guest to request invalidation of portions of a virtual TLB. For this, the hypercall parameter includes a list of GVAs that are supposed to be invalidated. However, when non-canonical GVAs are passed, there is currently no filtering in place and they are eventually passed to checked invocations of INVVPID on Intel / INVLPGA on AMD. While AMD's INVLPGA silently ignores non-canonical addresses (effectively a no-op), Intel's INVVPID explicitly signals VM-Fail and ultimately triggers the WARN_ONCE in invvpid_error(): invvpid failed: ext=0x0 vpid=1 gva=0xaaaaaaaaaaaaa000 WARNING: CPU: 6 PID: 326 at arch/x86/kvm/vmx/vmx.c:482 invvpid_error+0x91/0xa0 [kvm_intel] Modules linked in: kvm_intel kvm 9pnet_virtio irqbypass fuse CPU: 6 UID: 0 PID: 326 Comm: kvm-vm Not tainted 6.15.0 #14 PREEMPT(voluntary) RIP: 0010:invvpid_error+0x91/0xa0 [kvm_intel] Call Trace: vmx_flush_tlb_gva+0x320/0x490 [kvm_intel] kvm_hv_vcpu_flush_tlb+0x24f/0x4f0 [kvm] kvm_arch_vcpu_ioctl_run+0x3013/0x5810 [kvm] Hyper-V documents that invalid GVAs (those that are beyond a partition's GVA space) are to be ignored. While not completely clear whether this ruling also applies to non-canonical GVAs, it is likely fine to make that assumption, and manual testing on Azure confirms "real" Hyper-V interprets the specification in the same way. Skip non-canonical GVAs when processing the list of address to avoid tripping the INVVPID failure. Alternatively, KVM could filter out "bad" GVAs before inserting into the FIFO, but practically speaking the only downside of pushing validation to the final processing is that doing so is suboptimal for the guest, and no well-behaved guest will request TLB flushes for non-canonical addresses.

• https://git.kernel.org/stable/c/2d4dea3f76510c0afe3f18c910f647b816f7d566Patch
• https://git.kernel.org/stable/c/d5784ea45663330eaa868c518ea40e7a9f06aa2dPatch
• https://git.kernel.org/stable/c/f1b3ad11ec11c88ba9f79a73d27d4cda3f80fb24Patch
• https://git.kernel.org/stable/c/fa787ac07b3ceb56dd88a62d1866038498e96230Patch

Published

Jul 19, 2025

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2025-38346In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-38347In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38348In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-38349In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-3835Zohocorp ManageEngine Exchange Reporter Plus versions 5721 a…9.6
• CVE-2025-38350In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-38352In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-38353In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38354In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38355In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38356In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38357In the Linux kernel, the following vulnerability has been re…7.8