https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-14T22:38:48.053344+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2025-21970 CVE-2025-21970 — net/mlx5: Bridge, fix the crash caused by LAG state check 2026-10-14T22:38:48.087068+00:00

Affected: Linux

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

net/mlx5: Bridge, fix the crash caused by LAG state check

When removing LAG device from bridge, NETDEV_CHANGEUPPER event is triggered. Driver finds the lower devices (PFs) to flush all the offloaded entries. And mlx5_lag_is_shared_fdb is checked, it returns false if one of PF is unloaded. In such case, mlx5_esw_bridge_lag_rep_get() and its caller return NULL, instead of the alive PF, and the flush is skipped.

Besides, the bridge fdb entry's lastuse is updated in mlx5 bridge event handler. But this SWITCHDEV_FDB_ADD_TO_BRIDGE event can be ignored in this case because the upper interface for bond is deleted, and the entry will never be aged because lastuse is never updated.

To make things worse, as the entry is alive, mlx5 bridge workqueue keeps sending that event, which is then handled by kernel bridge notifier. It causes the following crash when accessing the passed bond netdev which is already destroyed.

To fix this issue, remove such checks. LAG state is already checked in commit 15f8f168952f ("net/mlx5: Bridge, verify LAG state when adding bond to bridge"), driver still need to skip offload if LAG becomes invalid state after initialization.

Oops: stack segment: 0000 [#1] SMP CPU: 3 UID: 0 PID: 23695 Comm: kworker/u40:3 Tainted: G OE 6.11.0_mlnx #1 Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebui…

 https://cve.radiocsirt.org/vuln/usn-7591-1 USN-7591-1 — linux, linux-gcp, linux-gke, linux-gkeop, linux-ibm, linux-kvm, linux-lowlatency, linux-nvidia, linux-nvidia-tegra, lin… 2026-10-14T22:38:48.087165+00:00

Affected: Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-kvm, Ubuntu:22.04:LTS: linux-lowlatency, Ubuntu:22.04:LTS: linux-nvidia, Ubuntu:22.04:LTS: linux-nvidia-tegra, Ubuntu:22.04:LTS: linux-nvidia-tegra-igx and 1 more

Michael Randrianantenaina discovered that the Bluetooth driver in the Linux Kernel contained an improper access control vulnerability. A nearby attacker could use this to connect a rougue device and possibly execute arbitrary code. (CVE-2024-8805)

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: - PowerPC architecture; - x86 architecture; - ACPI drivers; - Clock framework and drivers; - GPU drivers; - HID subsystem; - InfiniBand drivers; - Media drivers; - MemoryStick subsystem; - Network drivers; - Mellanox network drivers; - NTB driver; - PCI subsystem; - Voltage and Current Regulator drivers; - Remote Processor subsystem; - SCSI subsystem; - QCOM SoC drivers; - Thermal drivers; - BTRFS file system; - Ext4 file system; - JFS file system; - Network file system (NFS) server daemon; - NTFS3 file system; - File systems infrastructure; - Proc file system; - SMB network file system; - IPv6 networking; - RDMA verbs API; - SoC audio core drivers; - Tracing infrastructure; - Watch queue notification mechanism; - 802.1Q VLAN protocol; - Asynchronous Transfer Mo…