Bug 2543107 (CVE-2026-98164) - CVE-2026-98164 kernel: KVM: x86/mmu: Check write tracking in all address spaces
Summary: CVE-2026-98164 kernel: KVM: x86/mmu: Check write tracking in all address spaces
Keywords:
Status: NEW
Alias: CVE-2026-98164
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-29 12:52 UTC by OSIDB Bzimport
Modified: 2026-09-29 13:55 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-29 12:52:51 UTC
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]


Note You need to log in before you can comment on or make changes to this bug.