https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-25T02:10:28.552000+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-05363 bdu:2025-05363 2026-10-25T02:10:28.715849+00:00 bdu:2025-05363 https://cve.radiocsirt.org/vuln/bell-cve-2023-53037 BELL-CVE-2023-53037 2026-10-25T02:10:28.715888+00:00

Affected: Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0316 certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer… 2026-10-25T02:10:28.715916+00:00 certfr-2026-avi-0316 https://cve.radiocsirt.org/vuln/euvd-2026-311802 EUVD-2026-311802 2026-10-25T02:10:28.715932+00:00 EUVD-2026-311802 https://cve.radiocsirt.org/vuln/fkie_cve-2023-53037 fkie_cve-2023-53037 2026-10-25T02:10:28.715943+00:00

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

scsi: mpi3mr: Bad drive in topology results kernel crash

When the SAS Transport Layer support is enabled and a device exposed to the OS by the driver fails INQUIRY commands, the driver frees up the memory allocated for an internal HBA port data structure. However, in some places, the reference to the freed memory is not cleared. When the firmware sends the Device Info change event for the same device again, the freed memory is accessed and that leads to memory corruption and OS crash.

 https://cve.radiocsirt.org/vuln/ghsa-2px8-v868-2g2q GHSA-2px8-v868-2g2q 2026-10-25T02:10:28.715969+00:00

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

scsi: mpi3mr: Bad drive in topology results kernel crash

When the SAS Transport Layer support is enabled and a device exposed to the OS by the driver fails INQUIRY commands, the driver frees up the memory allocated for an internal HBA port data structure. However, in some places, the reference to the freed memory is not cleared. When the firmware sends the Device Info change event for the same device again, the freed memory is accessed and that leads to memory corruption and OS crash.

 https://cve.radiocsirt.org/vuln/msrc_cve-2023-53037 msrc_CVE-2023-53037 — scsi: mpi3mr: Bad drive in topology results kernel crash 2026-10-25T02:10:28.715999+00:00 msrc_CVE-2023-53037 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53037 UBUNTU-CVE-2023-53037 2026-10-25T02:10:28.716014+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 109 more

In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Bad drive in topology results kernel crash When the SAS Transport Layer support is enabled and a device exposed to the OS by the driver fails INQUIRY commands, the driver frees up the memory allocated for an internal HBA port data structure. However, in some places, the reference to the freed memory is not cleared. When the firmware sends the Device Info change event for the same device again, the freed memory is accessed and that leads to memory corruption and OS crash.