Linux kernel deadlock in GVE XSK pool disablement
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 |
|
|
6.18.577.2.117.3In the Linux kernel, the following vulnerability has been resolved:
gve: fix napi_disable deadlock when attempting to disable XSK pools
When disabling XSK pools, GVE calls the unlocked versions of napi_disable and napi_enable. However, the netdev lock has already been acquired before ndo_bpf is called because GVE supports queue management ops. Calling the unlocked versions of napi_disable/enable results in a deadlock when attempting to disable XSK pools, as the thread attempts to re-acquire a lock it already holds.
Update the NAPI calls to use the locked versions.
This issue was found in production.
From the CVE record · Linux
The Linux kernel’s gve driver can deadlock when disabling XSK pools because it tries to acquire a lock the calling thread already holds. The issue was found in production; the input does not describe an attacker path or specify network, authentication, or user-interaction requirements.
Engineers running Linux kernels with the gve driver should check their deployments; affected versions were not specified.