scsi: smartpqi: Fix device resources accessed after device removal
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2d80f4054f7f901b8ad97358a9069616ac8524c7 · < b518e86d1a70a88f6592a7c396cf1b93493d1aab| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: smartpqi: Fix device resources accessed after device removal
Correct possible race conditions during device removal.
Previously, a scheduled work item to reset a LUN could still execute after the device was removed, leading to use-after-free and other resource access issues.
This race condition occurs because the abort handler may schedule a LUN reset concurrently with device removal via sdev_destroy(), leading to use-after-free and improper access to freed resources.
- Check in the device reset handler if the device is still present in the controller's SCSI device list before running; if not, the reset is skipped.
- Cancel any pending TMF work that has not started in sdev_destroy().
- Ensure device freeing in sdev_destroy() is done while holding the LUN reset mutex to avoid races with ongoing resets.
From the CVE record · Linux
The Linux kernel’s smartpqi SCSI driver has a race during device removal. If an abort handler schedules a LUN reset while the device is being removed, the reset work can access freed resources; the input does not specify an attacker path or authentication requirements.
Engineers running Linux kernels with the smartpqi driver should check their versions; affected versions are not specified.