References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Known Affected Software Configurations Switch to CPE 2.2

Change History

AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CWE-476

OR
          *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 5.18.3

kernel.org: https://git.kernel.org/stable/c/baeb705fd6a7245cc1fa69ed991a9cffdf44a174 Types: Patch

kernel.org: https://git.kernel.org/stable/c/e7be3877589d539c52e5d1d23a625f889b541b9d Types: Patch

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

https://git.kernel.org/stable/c/baeb705fd6a7245cc1fa69ed991a9cffdf44a174

https://git.kernel.org/stable/c/e7be3877589d539c52e5d1d23a625f889b541b9d