scsi: mpi3mr: Bad drive in topology results kernel crash
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.1.226.2.96.3In 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.
From the CVE record · Linux
The Linux kernel’s mpi3mr SCSI driver can access freed memory when SAS Transport Layer support is enabled and a device fails INQUIRY commands. If firmware later sends another Device Info change event for that device, the access can corrupt memory and crash the OS. The input does not establish a network attack path, authentication requirement, or user-interaction requirement.
Engineers running Linux systems that use the mpi3mr driver with SAS Transport Layer support should check their kernel versions; affected versions are not specified.