vmxnet3: unregister xdp rxq info in the reset path
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:
vmxnet3: unregister xdp rxq info in the reset path
vmxnet3 does not unregister xdp rxq info in the vmxnet3_reset_work() code path as vmxnet3_rq_destroy() is not invoked in this code path. So, we get below message with a backtrace.
Missing unregister, handled but fix driver WARNING: CPU:48 PID: 500 at net/core/xdp.c:182 __xdp_rxq_info_reg+0x93/0xf0
This patch fixes the problem by moving the unregister code of XDP from vmxnet3_rq_destroy() to vmxnet3_rq_cleanup().
From the CVE record · Linux
The Linux kernel's vmxnet3 driver fails to unregister XDP receive-queue information during its reset path, producing a kernel warning and backtrace. The input does not describe an attacker action or specify network access, authentication, or user-interaction requirements.
Engineers running the Linux kernel with the vmxnet3 driver should check their systems; affected versions are not specified.