https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T20:39:39.914416+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-80625 Withdrawn: BELL-CVE-2026-80625 — CVE-2026-80625 does not affect BellSoft software 2026-10-03T20:39:39.921018+00:00

Withdrawn by the publisher.

https://cve.radiocsirt.org/vuln/euvd-2026-361021 EUVD-2026-361021 2026-10-03T20:39:39.921061+00:00 EUVD-2026-361021 https://cve.radiocsirt.org/vuln/fkie_cve-2026-80625 fkie_cve-2026-80625 2026-10-03T20:39:39.921077+00:00

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

RDMA/hns: Fix memory leak of bonding resources

In a corner case of concurrent driver removal and driver reset, bonding resource is first released in hns_roce_hw_v2_exit() during driver removal, and then is allocated again in hns_roce_register_device() during driver reset. This leads to memory leak because the release timing has already passed. This may also lead to a kernel panic as below because of the leaked notifier callback:

Call trace: 0xffffa20fccc04978 (P) raw_notifier_call_chain+0x20/0x38 call_netdevice_notifiers_info+0x60/0xb8 netdev_lower_state_changed+0x4c/0xb8

As Sashiko suggested, the teardown order of bonding resources should be inverted to make sure the resources are released when the driver is removed.

 https://cve.radiocsirt.org/vuln/ghsa-q7c4-mw3p-rvrq GHSA-q7c4-mw3p-rvrq 2026-10-03T20:39:39.921115+00:00

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

RDMA/hns: Fix memory leak of bonding resources

In a corner case of concurrent driver removal and driver reset, bonding resource is first released in hns_roce_hw_v2_exit() during driver removal, and then is allocated again in hns_roce_register_device() during driver reset. This leads to memory leak because the release timing has already passed. This may also lead to a kernel panic as below because of the leaked notifier callback:

Call trace: 0xffffa20fccc04978 (P) raw_notifier_call_chain+0x20/0x38 call_netdevice_notifiers_info+0x60/0xb8 netdev_lower_state_changed+0x4c/0xb8

As Sashiko suggested, the teardown order of bonding resources should be inverted to make sure the resources are released when the driver is removed.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80625 UBUNTU-CVE-2026-80625 2026-10-03T20:39:39.921138+00:00

Affected: Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 117 more

In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix memory leak of bonding resources In a corner case of concurrent driver removal and driver reset, bonding resource is first released in hns_roce_hw_v2_exit() during driver removal, and then is allocated again in hns_roce_register_device() during driver reset. This leads to memory leak because the release timing has already passed. This may also lead to a kernel panic as below because of the leaked notifier callback: Call trace: 0xffffa20fccc04978 (P) raw_notifier_call_chain+0x20/0x38 call_netdevice_notifiers_info+0x60/0xb8 netdev_lower_state_changed+0x4c/0xb8 As Sashiko suggested, the teardown order of bonding resources should be inverted to make sure the resources are released when the driver is removed.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075 WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T20:39:39.921350+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.