Stale nested-guest mappings via cross-CPU INVVPID
Published Sep 16, 2026 · Updated Sep 16, 2026
A TLB invalidation flaw in Linux KVM before 6.12.110, 6.18.51, and 7.2.5 allows guest OS users to retain stale nested-guest mappings. KVM emulates an L1 INVVPID with vpid02 on the current physical CPU rather than the CPU where L2 last ran, so that CPU's TLB entries remain unflushed. Reachability requires Intel VMX nested virtualization, an L2 exit, L1 migration across physical CPUs, INVVPID execution, and migration back; the published record specifies no consequence beyond stale translations.
Summary
What happened
A TLB invalidation flaw in Linux KVM before 6.12.110, 6.18.51, and 7.2.5 allows guest OS users to retain stale nested-guest mappings. KVM emulates an L1 INVVPID with vpid02 on the current physical CPU rather than the CPU where L2 last ran, so that CPU's TLB entries remain unflushed. Reachability requires Intel VMX nested virtualization, an L2 exit, L1 migration across physical CPUs, INVVPID execution, and migration back; the published record specifies no consequence beyond stale translations.
The record
- CVE
- CVE-2026-89929
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.12.110
- Affected versionversion=0 <6.18.51
- Affected versionversion=0 <7.2.5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <27bdeb5fd19046ffba9ff234e92fe553eb2efb30
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d00e67326d831e6e610933a3800712f4ffe6ec1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9941850e8adf164d005dbd3774c4b79e91a3cb8e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d03e721801ac54b9fdf05668aa0c069f07913b68
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo