ixgbe: Fix NULL pointer dereference in ethtool loopback test
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:
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.
From the CVE record · Linux
The Linux kernel's ixgbe driver can dereference a NULL pointer during an ethtool loopback test because the test ring has no associated q_vector. The input does not describe an attacker path or specify access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the ixgbe driver should check their versions; affected versions are not specified.