---
id: CVE-2026-98164
title: |-
  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…
summary: |-
  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…
severity: high
cvss: 7.1
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'
cwe:
  - CWE-670
  - CWE-617
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 4.2, < 6.1.187'
  - 'linux_kernel >= 6.2, < 6.6.156'
  - 'linux_kernel >= 6.7, < 6.12.108'
  - 'linux_kernel >= 6.13, < 6.18.49'
  - 'linux_kernel >= 6.19, < 7.1.13'
  - linux_kernel = 7.2
patched:
  - linux_kernel 7.1.13
published: '2026-09-29'
updated: '2026-10-07'
sourceUpdated: '2026-10-07T07:17:03.147'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-98164'
references:
  - url: 'https://git.kernel.org/stable/c/09aa68552d2542cc6c23edd1568ac265dc5d886f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/0f38453cdb2e17566ccb7c0f3dabd5bd21caca26'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/429b6f43b4d8c98988fdca99e02dc156134e3d77'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c0a9bd5fca0b5f2dea32b0fc31350e71e8648112'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d8636c8f9f95d0fd1e2f6f1cad0d5757aa6f212a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ec8fcaf354c1cbb36755d48e9f5a00c9591349e5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98164.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-98164'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2543107'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-98164'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-98164'
  - url: >-
      https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-98164.mbox
tags:
  - nvd
  - cve.org
  - csaf
  - vex
  - red-hat
epss: 0.00153
epssPercentile: 0.04374
ingestedAt: '2026-09-29T12:33:37.302Z'
scores:
  nvd: 7.1
  vendor: 5.5
---

## Overview

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]

## Affected

- `linux_kernel >= 4.2, < 6.1.187`
- `linux_kernel >= 6.2, < 6.6.156`
- `linux_kernel >= 6.7, < 6.12.108`
- `linux_kernel >= 6.13, < 6.18.49`
- `linux_kernel >= 6.19, < 7.1.13`
- `linux_kernel = 7.2`

## Remediation

Upgrade past the affected range:

- `linux_kernel 7.1.13`

## Vendor advisories

- **Red Hat VEX** · Moderate · affected: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4 · no fix planned: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4 · updated 2026-10-17 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98164.json)