3795 matches found
SUSE CVE-2026-64247
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank the TLFS allows for a maximum o...
PT-2026-64758
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the drm/hyperv component where the hyperv receive sub function processes VMBus packets without verifying the actual number of bytes written by the host into hv-recv bu...
CVE-2026-64247
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank the TLFS allows for a maximum o...
EUVD-2026-48656
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank the TLFS allows for a maximum o...
CVE-2026-64247 KVM: x86: hyper-v: Bound the bank index when querying sparse banks
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank the TLFS allows for a maximum o...
CVE-2026-64247
CVE-2026-64247 concerns the Linux kernel KVM code for x86 with hyper-v virtualization. The issue arises when checking if a VP ID is in a sparse bank set: the VP ID could be copied without bounds checking, risking an out-of-bounds read when testing the sparse bank and potentially triggering an unn...
CVE-2026-64247: Out-of-bounds Read
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank the TLFS allows for a maximum o...
Exploit for Heap-based Buffer Overflow in Microsoft
CVE-2025-21333 Hyper-V NT Kernel Integration VSP vkrnlintvs...
Microsoft Hyper-V netvsc Out-Of-Bounds Read Local Privilege Escalation Vulnerability
This vulnerability allows local attackers to escalate privileges on affected installations of Microsoft Hyper-V. An attacker must first obtain the ability to execute low-privileged code within a Windows virtual machine under Hyper-V in order to exploit this vulnerability. The specific flaw exists...
EUVD-2026-44137
Heap-based buffer overflow in Windows Hyper-V allows an authorized attacker to elevate privileges locally...
EUVD-2026-44096
Buffer over-read in Windows Hyper-V allows an authorized attacker to deny service over an adjacent network...
EUVD-2026-43997
Use after free in Windows Hyper-V allows an authorized attacker to elevate privileges locally...
EUVD-2026-43755
Use after free in Windows Hyper-V allows an unauthorized attacker to elevate privileges locally...
CVE-2026-50680
Heap-based buffer overflow in Windows Hyper-V allows an authorized attacker to elevate privileges locally...
CVE-2026-50485
Buffer over-read in Windows Hyper-V allows an authorized attacker to deny service over an adjacent network...
CVE-2026-54129
Use after free in Windows Hyper-V allows an authorized attacker to elevate privileges locally...
CVE-2026-54127
Use after free in Windows Hyper-V allows an unauthorized attacker to elevate privileges locally...
CVE-2026-50680 Windows Hyper-V Elevation of Privilege Vulnerability
...
CVE-2026-50680 Windows Hyper-V Elevation of Privilege Vulnerability
...
CVE-2026-50680
CVE-2026-50680 is a heap-based buffer overflow in Windows Hyper-V that enables local privilege escalation by an authorized attacker. The issue affects Hyper-V and is exploitable locally with high privileges required and no user interaction, per the CVE description and details in connected documen...