https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-10T14:44:26.941597+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2025-22013 CVE-2025-22013 — KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state 2026-10-10T14:44:27.062059+00:00

Affected: Linux

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

KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state

There are several problems with the way hyp code lazily saves the host's FPSIMD/SVE state, including:

* Host SVE being discarded unexpectedly due to inconsistent configuration of TIF_SVE and CPACR_ELx.ZEN. This has been seen to result in QEMU crashes where SVE is used by memmove(), as reported by Eric Auger:

https://issues.redhat.com/browse/RHEL-68997

* Host SVE state is discarded *after* modification by ptrace, which was an unintentional ptrace ABI change introduced with lazy discarding of SVE state.

* The host FPMR value can be discarded when running a non-protected VM, where FPMR support is not exposed to a VM, and that VM uses FPSIMD/SVE. In these cases the hyp code does not save the host's FPMR before unbinding the host's FPSIMD/SVE/SME state, leaving a stale value in memory.

Avoid these by eagerly saving and "flushing" the host's FPSIMD/SVE/SME state when loading a vCPU such that KVM does not need to save any of the host's FPSIMD/SVE/SME state. For clarity, fpsimd_kvm_prepare() is removed and the necessary call to fpsimd_save_and_flush_cpu_state() is placed in kvm_arch_vcpu_load_fp(). As 'fpsimd_state' and 'fpmr_ptr' should not be used, they are set to NULL; all uses of these will be removed in subsequent patches.

Historical problems go back at least as far as v5.17, e.g. erroneous assumptions about TIF_SVE being…

 https://cve.radiocsirt.org/vuln/usn-7605-1 USN-7605-1 — linux, linux-aws, linux-gcp, linux-gcp-6.11, linux-hwe-6.11, linux-oracle, linux-raspi, linux-realtime vulnerabilities 2026-10-10T14:44:27.062162+00:00

Affected: Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

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: - ARM32 architecture; - ARM64 architecture; - PowerPC architecture; - x86 architecture; - Compute Acceleration Framework; - ACPI drivers; - Ublk userspace block driver; - Compressed RAM block device driver; - Bus devices; - AMD CDX bus driver; - Clock framework and drivers; - DMA engine subsystem; - DPLL subsystem; - Qualcomm firmware drivers; - GPIO subsystem; - GPU drivers; - HID subsystem; - IIO subsystem; - InfiniBand drivers; - Multiple devices driver; - Media drivers; - MemoryStick subsystem; - Network drivers; - Mellanox network drivers; - NTB driver; - NVME drivers; - PCI subsystem; - Pin controllers subsystem; - RapidIO drivers; - Voltage and Current Regulator drivers; - Remote Processor subsystem; - SCSI subsystem; - SLIMbus drivers; - QCOM SoC drivers; - VideoCore services drivers; - Thermal drivers; - USB DSL drivers; - USB Host Controller drivers; - Renesas USBHS Controller drivers; - USB Type-C Connector System Software Interface driver; - Virtio Host (VHOST) subsystem; - Fr…