scsi: ufs: core: Fix invalid probe error return 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: ufs: core: Fix invalid probe error return value
After DME Link Startup, the error return value is set to the MIPI UniPro GenericErrorCode which can be 0 (SUCCESS) or 1 (FAILURE). Upon failure during driver probe, the error code 1 is propagated back to the driver probe function which must return a negative value to indicate an error, but 1 is not negative, so the probe is considered to be successful even though it failed. Subsequently, removing the driver results in an oops because it is not in a valid state.
This happens because none of the callers of ufshcd_init() expect a non-negative error code.
Fix the return value and documentation to match actual usage.
From the CVE record · Linux
The Linux kernel UFS core can return a positive error code when driver probe fails, causing the probe to be treated as successful. Removing the driver afterward can cause a kernel oops because the driver is in an invalid state. The input does not describe an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels with the UFS driver should check their versions; affected versions are not specified.