scsi: wd33c93: Don't use stale scsi_pointer value
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: wd33c93: Don't use stale scsi_pointer value
A regression was introduced with commit dbb2da557a6a ("scsi: wd33c93: Move the SCSI pointer to private command data") which results in an oops in wd33c93_intr(). That commit added the scsi_pointer variable and initialized it from hostdata->connected. However, during selection, hostdata->connected is not yet valid. Fix this by getting the current scsi_pointer from hostdata->selecting.
From the CVE record · Linux
A regression in the Linux kernel’s wd33c93 SCSI driver uses a stale SCSI pointer during selection, causing a kernel oops in wd33c93_intr(). The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with the wd33c93 SCSI driver should check their versions; affected versions are not specified.