8325 matches found
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...
USN-8609-1 linux-azure-fde-6.8 vulnerabilities
It was discovered that some AMD processors did not properly clear data in the floating point divider unit during speculative execution. A local attacker could use this to expose sensitive information. CVE-2025-54505 It was discovered that some AMD Zen 2 processors did not properly isolate shared...
USN-8596-1: Linux kernel (NVIDIA) vulnerabilities
It was discovered that some AMD processors did not properly clear data in the floating point divider unit during speculative execution. A local attacker could use this to expose sensitive information. CVE-2025-54505 It was discovered that some AMD Zen 2 processors did not properly isolate shared...
MINI-HPCV-6V6F-HPV9
Bulletin has no description...
SUSE CVE-2026-64134
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Don't setup bogus ioviter for silencing At transition to the ioviter for PCM data transfer, we blindly applied the ioviter setup also for silencing i.e. data = NULL, and it leads to a calculation of bogus ioviter...
CVE-2026-64082
A flaw was found in the Linux kernel, specifically within the RISC-V architecture's handling of process tracing and signal restoration. When functions like compatriscvgprset or compatrestoresigcontext are invoked, they may process uninitialized stack data if a preceding user data copy operation...
USN-8566-1 linux, linux-gcp, linux-gke, linux-realtime vulnerabilities
It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a higher privilege level, resulting in privilege escalation. CVE-2025-54518 Several security issues...
CVE-2026-64134
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Don't setup bogus ioviter for silencing At transition to the ioviter for PCM data transfer, we blindly applied the ioviter setup also for silencing i.e. data = NULL, and it leads to a calculation of bogus ioviter...
CVE-2026-64134 ALSA: pcm: Don't setup bogus iov_iter for silencing
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Don't setup bogus ioviter for silencing At transition to the ioviter for PCM data transfer, we blindly applied the ioviter setup also for silencing i.e. data = NULL, and it leads to a calculation of bogus ioviter...
EUVD-2026-45819
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Don't setup bogus ioviter for silencing At transition to the ioviter for PCM data transfer, we blindly applied the ioviter setup also for silencing i.e. data = NULL, and it leads to a calculation of bogus ioviter...
CVE-2026-64134 ALSA: pcm: Don't setup bogus iov_iter for silencing
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Don't setup bogus ioviter for silencing At transition to the ioviter for PCM data transfer, we blindly applied the ioviter setup also for silencing i.e. data = NULL, and it leads to a calculation of bogus ioviter...
CVE-2026-64134
The CVE-2026-64134 entry concerns the Linux kernel ALSA PCM path. The vulnerability arises during transition to iov_iter for PCM data transfer, where iov_iter was also configured for silencing (data = NULL), leading to a bogus iov_iter calculation and a NULL dereference on some architectures, not...
PT-2026-61451
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the ALSA PCM data transfer process where the iov iter setup is incorrectly applied during silencing when data is NULL. This leads to the calculation of a bogus iov ite...
USN-8547-1 linux-gcp-5.15, linux-intel-iotg-5.15 vulnerabilities
Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - RISC-V architecture; - Cryptographic API; - InfiniBand drivers; - IOMMU subsystem; - Network drivers; -...
CVE-2026-15775
CVE-2026-15775 affects Google Chrome's V8 under a pre-150.0.7871.125 build. The issue is an inappropriate implementation that allowed a remote attacker to bypass the same-origin policy via a crafted HTML page. Impact is described as high in Chromium notes, with exploitation requiring user interac...