CVE-2023-53037
published 2025-05-02CVE-2023-53037: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Bad drive in topology results kernel crash When the SAS Transport Layer…
PriorityP341high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.18%
8.2th percentile
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.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.25-1 (bookworm) | linux 6.1.25-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df < 1f822ae8fb2a20fffa71e9bfa9b203c03d72d3ba | 1f822ae8fb2a20fffa71e9bfa9b203c03d72d3ba |
| linux | linux | >= c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df < aa11e4b6cdb403b9fdef6939550f6b36dd61624d | aa11e4b6cdb403b9fdef6939550f6b36dd61624d |
| linux | linux | >= c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df < 8e45183978d64699df639e795235433a60f35047 | 8e45183978d64699df639e795235433a60f35047 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 0 < 6.1.25-1 | 6.1.25-1 |
| linux | linux_kernel | >= 5.14 < 6.1.22 | 6.1.22 |
| linux | linux_kernel | >= 6.2 < 6.2.9 | 6.2.9 |
| msrc | cbl2_kernel_5.15.186.1-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_kernel_5.15.200.1-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_kernel_5.15.202.1-1_on_cbl_mariner_2.0 | — | — |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
vendor_msrc4.1MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Microsoft
scsi: mpi3mr: Bad drive in topology results kernel crash
vendor_msrc·2025-05-13·CVSS 4.1
CVE-2023-53037 [HIGH] CWE-416 scsi: mpi3mr: Bad drive in topology results kernel crash
scsi: mpi3mr: Bad drive in topology results kernel crash
Mariner: Mariner
Linux: Linux
Customer Action Required: Yes
Red Hat
kernel: scsi: mpi3mr: Bad drive in topology results kernel crash
vendor_redhat·2025-05-02·CVSS 7.8
CVE-2023-53037 [HIGH] kernel: scsi: mpi3mr: Bad drive in topology results kernel crash
kernel: scsi: mpi3mr: Bad drive in topology results kernel crash
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.
Statement: Fixes a use-after-free issue in the mpi3mr driver when a faulty device causes a stale pointer to be reused, leading to memory corruption and kernel crash. Requires
Debian
CVE-2023-53037: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3m...
vendor_debian·2023·CVSS 7.8
CVE-2023-53037 [HIGH] CVE-2023-53037: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3m...
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.
Scope: local
bookworm: resolved (fixed in 6.1.25-1)
bullseye: resolved
forky: resolved (fixed in 6.1.25-1)
sid: resolved (fixed in 6.1.25-1)
trixie: resolved (fixed in 6.1.25-1)
OSV
CVE-2023-53037: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Bad drive in topology results kernel crash When the SAS Transport La
osv·2025-05-02·CVSS 7.8
CVE-2023-53037 [HIGH] CVE-2023-53037: In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Bad drive in topology results kernel crash When the SAS Transport La
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.
GHSA
GHSA-2px8-v868-2g2q: In the Linux kernel, the following vulnerability has been resolved:
scsi: mpi3mr: Bad drive in topology results kernel crash
When the SAS Transport
ghsa_unreviewed·2025-05-02
CVE-2023-53037 [HIGH] CWE-416 GHSA-2px8-v868-2g2q: In the Linux kernel, the following vulnerability has been resolved:
scsi: mpi3mr: Bad drive in topology results kernel crash
When the SAS Transport
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.
No detection rules found.
No public exploits indexed.
2025-05-02
Published