https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-15T08:23:51.027629+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2025-37936 CVE-2025-37936 — perf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value. 2026-10-15T08:23:51.115093+00:00

Affected: Linux

In the Linux kernel, the following vulnerability has been resolved:

perf/x86/intel: KVM: Mask PEBS_ENABLE loaded for guest with vCPU's value.

When generating the MSR_IA32_PEBS_ENABLE value that will be loaded on VM-Entry to a KVM guest, mask the value with the vCPU's desired PEBS_ENABLE value. Consulting only the host kernel's host vs. guest masks results in running the guest with PEBS enabled even when the guest doesn't want to use PEBS. Because KVM uses perf events to proxy the guest virtual PMU, simply looking at exclude_host can't differentiate between events created by host userspace, and events created by KVM on behalf of the guest.

Running the guest with PEBS unexpectedly enabled typically manifests as crashes due to a near-infinite stream of #PFs. E.g. if the guest hasn't written MSR_IA32_DS_AREA, the CPU will hit page faults on address '0' when trying to record PEBS events.

The issue is most easily reproduced by running `perf kvm top` from before commit 7b100989b4f6 ("perf evlist: Remove __evlist__add_default") (after which, `perf kvm top` effectively stopped using PEBS). The userspace side of perf creates a guest-only PEBS event, which intel_guest_get_msrs() misconstrues a guest-*owned* PEBS event.

Arguably, this is a userspace bug, as enabling PEBS on guest-only events simply cannot work, and userspace can kill VMs in many other ways (there is no danger to the host). However, even if this is considered to be bad userspace behavior, there's zero downside t…

 https://cve.radiocsirt.org/vuln/usn-7649-1 USN-7649-1 — linux, linux-gcp, linux-raspi, linux-realtime vulnerabilities 2026-10-15T08:23:51.115233+00:00

Affected: Ubuntu:25.04: linux, Ubuntu:25.04: linux-gcp, Ubuntu:25.04: linux-raspi, Ubuntu:25.04: linux-realtime

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: - ARM64 architecture; - PA-RISC architecture; - PowerPC architecture; - S390 architecture; - x86 architecture; - Compute Acceleration Framework; - Ublk userspace block driver; - Bluetooth drivers; - ARM SCMI message protocol; - GPU drivers; - IOMMU subsystem; - IRQ chip drivers; - Multiple devices driver; - Network drivers; - PCI subsystem; - PTP clock framework; - SPI subsystem; - BTRFS file system; - SMB network file system; - eXpress Data Path; - Universal MIDI packet (UMP) support module; - Tracing infrastructure; - Memory management; - IPv4 networking; - IPv6 networking; - Network traffic control; - AMD SoC Alsa drivers; - SoC Audio generic drivers; (CVE-2025-37898, CVE-2025-37990, CVE-2025-37974, CVE-2025-37991, CVE-2025-37894, CVE-2025-37906, CVE-2025-37896, CVE-2025-37909, CVE-2025-37923, CVE-2025-37899, CVE-2025-37901, CVE-2025-37914, CVE-2025-38216, CVE-2025-37931, CVE-2025-37928, CVE-2025-37916, CVE-2025-37908, CVE-2025-37915, CVE-2025-37917, CVE-2025-37921, CVE-2025-37903, CVE-2025-37922, CVE-2025-37895, CVE-2025-37936, CVE-2025-37933, CVE-2025-37891, CVE-2025-37926, CVE-2025-37912, CVE-2025-37920, CVE-2025-37924, CVE-2025-37927, CVE-2025-37946, CVE-2025-37907, CVE-2025-37930, CVE-2025-37911, CVE-2025-37905, CVE-2025-37900, CVE-202…