CVE-2026-98164
In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Check write…
- Risk score
- 44/100
- CVSS
- 5.5 v3.1
- Exploit chance (30 days)
- 0.1%
- Published
- 29 Sep 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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-…
- Affected
- Linux kernel
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Story map
At a glance
Linux kernel: Amber, patch this week. In the Linux kernel, the following vulnerability has been resolved: sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START The SCTP_CMD_TIMER_START handler checks timer_pending() before calling timer_reduce(). The timer can expire and detach between these operations, causing timer_reduce() to rearm the timer without taking t…
The flaws
- CVE-2026-98164: In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Check write… (CVSS 5.5 · EPSS 0%)
- CVE-2026-98130: Race condition (CVSS 8.1 · EPSS 0%)
- CVE-2026-98115: Race condition (CVSS 8.8 · EPSS 0%)
- CVE-2026-98052: In the Linux kernel, the following vulnerability has been resolved: net: bcmasp: clear txcb->last… (CVSS 7.8 · EPSS 0%)
The fix
Fix: Apply the vendor's security update; see the linked advisory.
Who is exposed: Linux kernel
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-670 (CWE-670). 5 other warnings in 30 days
- Same product: Earlier Linux kernel warnings. 61 in the last 90 days
Why it is Yellow
- CVSS 5.5 medium
- On your watchlist: linux kernel
References
- https://git.kernel.org/stable/c/09aa68552d2542cc6c23edd1568ac265dc5d886f
- https://git.kernel.org/stable/c/0f38453cdb2e17566ccb7c0f3dabd5bd21caca26
- https://git.kernel.org/stable/c/429b6f43b4d8c98988fdca99e02dc156134e3d77
- https://git.kernel.org/stable/c/c0a9bd5fca0b5f2dea32b0fc31350e71e8648112
- https://git.kernel.org/stable/c/d8636c8f9f95d0fd1e2f6f1cad0d5757aa6f212a
- https://git.kernel.org/stable/c/ec8fcaf354c1cbb36755d48e9f5a00c9591349e5
Original 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]
Last activity 29 Sep 2026. Patch Forecast updates every hour.