All CVEs — page 650 of 678
The complete archive, 25 per page, newest first. 16938 records. Search instead.
This flaw allows an attacker to use stale TLB entries from a previous VM's VPID, potentially leading to data leakage or execution of malicious code.
This flaw allows an attacker to cause a local TLB flush on a failed nested VM-Enter, potentially leading to information disclosure, integrity issues, and availability problems.
The flaw allows INVVPID to be emulated on a different physical CPU than the one L2 is running on, leading to potential TLB entry invalidation issues.
The flaw allows a writer holding mmu_lock for write to free a pte_list_desc chain that a lockless walker is following, potentially leading to a use-after-free condition.
This vulnerability allows a local attacker to exploit a race condition in the Linux kernel's KVM s390 implementation when importing watchpoint data, potentially leading to kernel memory corruption or privilege escalation.
This vulnerability in the Linux kernel's KVM s390 implementation allows for potential memory corruption by improperly handling machine checks related to the channel subsystem. It matters because it could lead to arbitrary code execution if exploited.
The flaw allows concurrent access to the gmap->asce value while it is being modified, leading to potential memory corruption.
The flaw involves a TLB invalidation vulnerability in the Linux kernel's KVM arm64 implementation, where address rollover is not properly handled, leading to potential memory corruption or privilege escalation.
This vulnerability in the Linux kernel's KVM arm64 implementation allows a virtual CPU (vCPU) to encounter an invalid TLB entry due to concurrent modifications, potentially leading to data corruption or execution of malicious code within the virtualized environment.
The flaw lies in the global VNCR mapping counter used for TLB invalidation in the Linux kernel's KVM arm64 implementation, leading to potential missed invalidations and failure to invalidate VNCR pseudo TLBs.
This vulnerability in the Linux kernel's KVM arm64 implementation allows attackers to perform range-based TLBI invalidation without proper sign extension, potentially leading to privilege escalation.
This flaw allows a concurrent path to dereference a freed LPI, leading to potential memory corruption or execution of arbitrary code.
This vulnerability allows a guest operating system to potentially overflow a TLB invalidation range, leading to a potential privilege escalation or denial of service condition.