CVE-2023-53037: 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-53037?
CVE-2023-53037 is categorized as a high-severity vulnerability due to its potential to cause kernel crashes.
How do I fix CVE-2023-53037?
To resolve CVE-2023-53037, update your Linux kernel to the latest version that includes the necessary patches.
What systems are affected by CVE-2023-53037?
CVE-2023-53037 affects Linux kernels that utilize the SAS Transport Layer support.
What are the symptoms of CVE-2023-53037?
The primary symptom of CVE-2023-53037 is a kernel crash triggered by a bad drive in the topology.
Who is responsible for addressing CVE-2023-53037?
The Linux kernel development community is responsible for patching CVE-2023-53037 and providing updates.