Skip to content
Noroxi
CVE-2026-98164· CVE.org (no NVD analysis yet)· CNA Linux

KVM: x86/mmu: Check write tracking in all address spaces

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Check write tracking in all address spaces kvm_gfn_is_write_tracked() checks only the supplied memslot, but page tracking is per-address-space and shadow pages are shared across all address spaces. With SMM, a GFN can therefore be write-tracked in one address space and appear untracked through the other. Check the supplied slot first, then the slot for the other address space. This ensures all callers honor write tracking regardless of the active address space. In particular, it prevents mmu_try_to_unsync_pages() from marking an upper-level shadow page unsync and eventually triggering the BUG in pte_list_remove(). [invert direction of the conditional. - Paolo]

—No exploit Fix available
Published
Sep 29, 2026
Updated
Sep 30, 2026
EPSS
0.2% · 8th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

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.2affected
    • 699023e239658e62da6f42f47d31b54788521ec1 and later · before 09aa68552d2542cc6c23edd1568ac265dc5d886faffected · git
    • 699023e239658e62da6f42f47d31b54788521ec1 and later · before 429b6f43b4d8c98988fdca99e02dc156134e3d77affected · git
    • 699023e239658e62da6f42f47d31b54788521ec1 and later · before d8636c8f9f95d0fd1e2f6f1cad0d5757aa6f212aaffected · git
    • 699023e239658e62da6f42f47d31b54788521ec1 and later · before c0a9bd5fca0b5f2dea32b0fc31350e71e8648112affected · git
    • 699023e239658e62da6f42f47d31b54788521ec1 and later · before ec8fcaf354c1cbb36755d48e9f5a00c9591349e5affected · git
    • 699023e239658e62da6f42f47d31b54788521ec1 and later · before 0f38453cdb2e17566ccb7c0f3dabd5bd21caca26affected · git
    • before 4.2not affected · semver
    • 6.1.187 and later · up to and including 6.1.*not affected · semver
    • 6.6.156 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.1.13-17.1.13-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
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

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 Linux09aa68552d2542cc6c23edd1568ac265dc5d886fVendor (CNA)
Linux Linux0f38453cdb2e17566ccb7c0f3dabd5bd21caca26Vendor (CNA)
Linux Linux429b6f43b4d8c98988fdca99e02dc156134e3d77Vendor (CNA)
Linux Linuxc0a9bd5fca0b5f2dea32b0fc31350e71e8648112Vendor (CNA)
Linux Linuxd8636c8f9f95d0fd1e2f6f1cad0d5757aa6f212aVendor (CNA)
Linux Linuxec8fcaf354c1cbb36755d48e9f5a00c9591349e5Vendor (CNA)
debian:linux6.1.187-1 · Debian:12Package 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.

  1. Published
  2. Fix recordedsame day
  3. TodayOct 2, 2026+3 d
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).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

  1. Exploit maturity— → none
  2. Fix✗ → ✓

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

References

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

All records