CVE-2026-99713: KVM: x86/mmu: Conditionally resched when retrying gPTE walk on A/D update failure

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

KVM: x86/mmu: Conditionally resched when retrying gPTE walk on A/D update failure

Conditionally reschedule when retrying a guest PTE walk because the CMPXCHG to update A/D bits failed, e.g. because a different task/vCPU modified the relevant gPTEs. On kernels without involuntary preemption of some kind, a misbehaving guest can "capture" a pCPU effectively indefinitely and trigger soft lockups by continuously modifying its gPTEs such that the result of the walk is remains valid.

Affected Software

3 affected componentsFixes available
linux/kernel>=2.6.25<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems running KVM on x86 are exposed when they use kernels without some form of involuntary preemption. The issue requires a guest capable of repeatedly modifying its guest page tables while KVM is walking them.

2

What can a malicious or misbehaving guest do?

A guest can repeatedly cause KVM's compare-and-exchange update of accessed/dirty bits to fail while keeping the page-table walk valid. This can effectively monopolize a physical CPU indefinitely and trigger soft lockups.

3

Is this a host-local issue or can it be triggered remotely?

The described trigger is a guest workload modifying its own guest PTEs, so exploitation requires the ability to run or control code in a KVM guest. The provided information does not describe a host-local unprivileged trigger or a network-only attack path.

4

What is the relevant mitigation if patching cannot happen immediately?

Use a kernel configuration that provides involuntary preemption, where applicable. This reduces the condition described as allowing a guest to retain a physical CPU effectively indefinitely.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203