CVE-2026-89929· NVD / CVE Program· CNA Linux

KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU

Noroxi assessment

Priority: Monitor (action score 35/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.16% (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 27bdeb5fd19046ffba9ff234e92fe553eb2efb30, 6d00e67326d831e6e610933a3800712f4ffe6ec1, 9941850e8adf164d005dbd3774c4b79e91a3cb8e; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 27bdeb5fd19046ffba9ff234e92fe553eb2efb30, 6d00e67326d831e6e610933a3800712f4ffe6ec1, 9941850e8adf164d005dbd3774c4b79e91a3cb8e; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: nVM: Ensure INVVPID is emulated on the correct physical CPU When emulating INVVPID, KVM executes INVVPID on the physical CPU using vpid02 (instead of the L1 assigned VPID), after doing some validations on the operands. However, it is possible that the physical CPU KVM executes INVVPID on is different from the CPU L2 is running on. For example, in the following scenario: - L2 runs on CPU #1 and exits to L1 (vmx->nested.vmcs02.cpu=1) - L1 migrates to CPU #2 and executes INVVPID - KVM executes INVVPID on CPU #2 - L1 migrates back to CPU #1 and runs L2 (vmx->nested.vmcs02.cpu=1) The TLB entries on CPU #1 are never invalidated, because INVVPID was executed on CPU #2, and vmcs02 never ran on a different pCPU (i.e. vmx_vcpu_load_vmcs() will *not* request KVM_REQ_TLB_FLUSH). Ensure that INVVPID is being executed on the same pCPU that L2 last ran on, and if not, fallback to clearing last_vpid=0 to trigger a full VPID flush on the next nested VM-Enter (as KVM will detect L1 using a different VPID for L2). If L2 ends up running on a different pCPU, KVM will flush the TLB anyway through vmx_vcpu_load_vmcs().

HighCVSS 8.8 · v3.1—No exploit Fix available

EUVD-2026-80529

Published: Sep 16, 2026
Updated: Oct 19, 2026
EPSS: 0.1% · 5th percentile
CWE: —

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: —
CNA · Linux: 8.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Running WordPress? Scan your site free with WP Lens

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.

—

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
- 4.4affected
- 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and later · before d03e721801ac54b9fdf05668aa0c069f07913b68affected · git
- 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and later · before 27bdeb5fd19046ffba9ff234e92fe553eb2efb30affected · git
- 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and later · before 9941850e8adf164d005dbd3774c4b79e91a3cb8eaffected · git
- 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 and later · before 6d00e67326d831e6e610933a3800712f4ffe6ec1affected · git
- before 4.4not affected · semver
- 6.12.110 and later · up to and including 6.12.*not affected · semver
- 6.18.51 and later · up to and including 6.18.*not affected · semver
- 7.2.5 and later · up to and including 7.2.*not affected · semver
- 7.3 and laternot affected · original_commit_for_fix

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	linux	from 0	—
Debian:12	linux-6.12	before 6.12.111-1~deb12u1	6.12.111-1~deb12u1
Debian:13	linux	before 6.12.111-1	6.12.111-1
Debian:14	linux	before 7.2.6-1	7.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
40Plan
CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
40Plan
CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-89927Sep 16, 2026 · KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock
28Monitor
← EarlierCVE-2026-89928Sep 16, 2026 · KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk
35Monitor
Later →CVE-2026-89930Sep 16, 2026 · KVM: nVMX: Service local TLB flushes on failed nested VM-Enter
37Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Linux Linux	27bdeb5fd19046ffba9ff234e92fe553eb2efb30	Vendor (CNA)
Linux Linux	6d00e67326d831e6e610933a3800712f4ffe6ec1	Vendor (CNA)
Linux Linux	9941850e8adf164d005dbd3774c4b79e91a3cb8e	Vendor (CNA)
Linux Linux	d03e721801ac54b9fdf05668aa0c069f07913b68	Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0	—	Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0	Release Notes	Microsoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0	Release Notes	Microsoft (MSRC)
debian:linux	6.12.111-1 · Debian:13	Package registry (OSV)
debian:linux-6.12	6.12.111-1~deb12u1 · Debian:12	Package registry (OSV)

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

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: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Changed
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

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.

Change log

Fix✗ → ✓Sep 28, 2026, 10:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/27bdeb5fd19046ffba9ff234e92fe553eb2efb30

Show all references (3 more)

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

All records