HomeDefectsLIN1024-10484
Fixed

LIN1024-10484 : Security Advisory - linux - CVE-2025-38351

Created: Jul 20, 2025    Updated: Oct 21, 2025
Resolved Date: Oct 9, 2025
Found In Version: 10.24.33.1
Fix Version: 10.24.33.13
Severity: Standard
Applicable for: Wind River Linux LTS 24
Component/s: Kernel

Description

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

CREATE(Triage):(User=admin) [CVE-2025-38351 (https://nvd.nist.gov/vuln/detail/CVE-2025-38351)

CVEs