CVE-2026-98164

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

  • High 7.1

Description

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]

Key facts

Published
29 Sep 2026
Last changed
7 Oct 2026
Assigned by
Linux
EPSS
0.153% likely to be exploited in the next 30 days, higher than 4.476% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.1CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 699023e239658e62da6f42f47d31b54788521ec1 up to but excluding 09aa68552d2542cc6c23edd1568ac265dc5d886f (affected)
  • 699023e239658e62da6f42f47d31b54788521ec1 up to but excluding 429b6f43b4d8c98988fdca99e02dc156134e3d77 (affected)
  • 699023e239658e62da6f42f47d31b54788521ec1 up to but excluding d8636c8f9f95d0fd1e2f6f1cad0d5757aa6f212a (affected)
  • 699023e239658e62da6f42f47d31b54788521ec1 up to but excluding c0a9bd5fca0b5f2dea32b0fc31350e71e8648112 (affected)
  • 699023e239658e62da6f42f47d31b54788521ec1 up to but excluding ec8fcaf354c1cbb36755d48e9f5a00c9591349e5 (affected)
  • 699023e239658e62da6f42f47d31b54788521ec1 up to but excluding 0f38453cdb2e17566ccb7c0f3dabd5bd21caca26 (affected)
LinuxLinux
  • Default status: affected
  • 4.2 (affected)
  • 0 up to but excluding 4.2 (unaffected)
  • 6.1.187 up to and including 6.1.* (unaffected)
  • 6.6.156 up to and including 6.6.* (unaffected)
  • 6.12.108 up to and including 6.12.* (unaffected)
  • 6.18.49 up to and including 6.18.* (unaffected)
  • 7.1.13 up to and including 7.1.* (unaffected)
  • 7.2 up to and including * (unaffected)

Timeline

  1. 29 Sep 2026 Published

References