In the Linux kernel, the following vulnerability has been resolved: ixgbe: Fix NULL pointer dereference in ethtool loopback test The ixgbe driver currently generates a NULL pointer dereference when performing the ethtool loopback test. This is due to the fact that there isn't a q_vector associated with the test ring when it is setup as interrupts are not normally added to the test rings. To address this I have added code that will check for a q_vector before returning a napi_id value. If a q_vector is not present it will return a value of 0. https://git.kernel.org/stable/c/31166efb1cee348eb6314e9c0095d84cbeb66b9d https://git.kernel.org/stable/c/758d19098df4b0bbca9f40d6ae6c82c9c18b9bba
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2266381]
This was fixed for Fedora with the 5.11.16 stable kernel update.
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2021-46916 is: CHECK Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags REMOTE NULLPTR SIMPLEFIX NETWORK IMPROVEONLY ; these flags parsed automatically based on patche data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.