Answer in brief
CVE-2023-53037 records a High severity (CVSS 7.8) vulnerability in scsi: mpi3mr: Bad drive in topology results kernel crash. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df <1f822ae8fb2a20fffa71e9bfa9b203c03d72d3ba || >=c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df <aa11e4b6cdb403b9fdef6939550f6b36dd61624d || >=c4f7ac64616ee513f9ac4ae6c4d8c3cccb6974df <8e45183978d64699df639e795235433a60f35047 | 1f822ae8fb2a20fffa71e9bfa9b203c03d72d3ba, aa11e4b6cdb403b9fdef6939550f6b36dd61624d, 8e45183978d64699df639e795235433a60f35047 |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
May 2, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.