Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-98164

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

High7.1EPSS 0.15%
Published
Updated
Reserved
Assigned by
Linux

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]

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 8 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-98164, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Weakness

Affected products

  • Linux · Linux

    • affected 699023e239658e62da6f42f47d31b54788521ec1 – < 09aa68552d2542cc6c23edd1568ac265dc5d886f
    • affected 699023e239658e62da6f42f47d31b54788521ec1 – < 429b6f43b4d8c98988fdca99e02dc156134e3d77
    • affected 699023e239658e62da6f42f47d31b54788521ec1 – < d8636c8f9f95d0fd1e2f6f1cad0d5757aa6f212a
    • affected 699023e239658e62da6f42f47d31b54788521ec1 – < c0a9bd5fca0b5f2dea32b0fc31350e71e8648112
    • affected 699023e239658e62da6f42f47d31b54788521ec1 – < ec8fcaf354c1cbb36755d48e9f5a00c9591349e5
    • affected 699023e239658e62da6f42f47d31b54788521ec1 – < 0f38453cdb2e17566ccb7c0f3dabd5bd21caca26
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.156 – ≤ 6.6.*
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.18.49 – ≤ 6.18.*
    • unaffected 7.1.13 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98164 badge
[![CVE-2026-98164](https://trackcve.app/badge/CVE-2026-98164.svg)](https://trackcve.app/cve/CVE-2026-98164)

Record last updated .