CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's KVM module, specifically in the handling of write tracking across different address spaces, which could lead to inconsistencies in memory management. This flaw may allow unauthorized access to write-tracked memory pages, potentially compromising system integrity and security. Organizations utilizing Linux-based systems with KVM should prioritize addressing this issue to mitigate risks associated with memory management vulnerabilities.
Original NVD 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]
Related CVEs
Other vulnerabilities affecting the same vendor(s)