Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38351: KVM: x86/hyper-v: Skip non-canonical addresses during PV TLB flush

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2d4dea3f76510c0afe3f18c910f647b816f7d566, d5784ea45663330eaa868c518ea40e7a9f06aa2d, f1b3ad11ec11c88ba9f79a73d27d4cda3f80fb24.

Low priority for now. Upgrade to Linux Linux 2d4dea3f76510c0afe3f18c910f647b816f7d566, d5784ea45663330eaa868c518ea40e7a9f06aa2d, f1b3ad11ec11c88ba9f79a73d27d4cda3f80fb24 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 19, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38351

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.2affected
    • 260970862c88b4130e9e12be023c7e2c2d37a966 and later · before d5784ea45663330eaa868c518ea40e7a9f06aa2daffected · git
    • 260970862c88b4130e9e12be023c7e2c2d37a966 and later · before f1b3ad11ec11c88ba9f79a73d27d4cda3f80fb24affected · git
    • 260970862c88b4130e9e12be023c7e2c2d37a966 and later · before 2d4dea3f76510c0afe3f18c910f647b816f7d566affected · git
    • 260970862c88b4130e9e12be023c7e2c2d37a966 and later · before fa787ac07b3ceb56dd88a62d1866038498e96230affected · git
    • before 6.2not affected · semver
    • 6.6.103 and later · up to and including 6.6.*not affected · semver
    • 6.12.41 and later · up to and including 6.12.*not affected · semver
    • 6.15.7 and later · up to and including 6.15.*not affected · semver
    • 6.16 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.2 and later · before 6.6.103
  • linux linux kernel6.7 and later · before 6.12.41
  • linux linux kernel6.13 and later · before 6.15.7
  • linux linux kernel6.16

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.40.1.el10_06.12.0-55.40.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.40.1.el10_06.12.0-55.40.1.el10_0
AlmaLinux:9kernelbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64kbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-corebefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-debugbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-develbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-corebefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-cross-headersbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-debugbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-debug-corebefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-debug-develbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-570.51.1.el9_65.14.0-570.51.1.el9_6

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38349Jul 18, 2025 · eventpoll: don't decrement ep refcount while still holding the ep mutex
    31Monitor
  • ← EarlierCVE-2025-38350Jul 19, 2025 · net/sched: Always pass notifications when child class becomes empty
    31Monitor
  • Later →CVE-2025-38352Jul 22, 2025 · posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()KEV
    61This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2d4dea3f76510c0afe3f18c910f647b816f7d566Vendor (CNA)
Linux Linuxd5784ea45663330eaa868c518ea40e7a9f06aa2dVendor (CNA)
Linux Linuxf1b3ad11ec11c88ba9f79a73d27d4cda3f80fb24Vendor (CNA)
Linux Linuxfa787ac07b3ceb56dd88a62d1866038498e96230Vendor (CNA)
almalinux:kernel5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-570.51.1.el9_6 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.41-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-570.51.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:6.12.0-55.40.1.el10_0 · Rocky Linux:10Package registry (OSV)

+12

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records