ice: always check VF VSI pointer values
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:
ice: always check VF VSI pointer values
The ice_get_vf_vsi function can return NULL in some cases, such as if handling messages during a reset where the VSI is being removed and recreated.
Several places throughout the driver do not bother to check whether this VSI pointer is valid. Static analysis tools maybe report issues because they detect paths where a potentially NULL pointer could be dereferenced.
Fix this by checking the return value of ice_get_vf_vsi everywhere.
From the CVE record · Linux
The Linux kernel ice driver does not always check whether ice_get_vf_vsi returns NULL. This can happen while messages are handled during a reset, when a VSI is being removed and recreated, and may lead to a NULL pointer dereference. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the ice driver should check whether their builds include the fix; affected versions are not specified.