CVE-2022-3344 (2022)
A reset signal pulled a virtual CPU out of a nested guest, and KVM kept running on the nested guest's control block, which was then freed. The fix switched execution back to the parent VM's control block before anything was released.
KVM stopped running on a freed control block.
The fix left the page-table pointer inside that block unrefreshed, and the code path has since needed at least two follow-on fixes.
CVE-2026-99312 is one of those follow-ons: same reset path, same pointer, four years later.
