gve: Clear napi->skb before dev_kfree_skb_any()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gve: Clear napi->skb before dev_kfree_skb_any()
gve_rx_free_skb incorrectly leaves napi->skb referencing an skb after it is freed with dev_kfree_skb_any(). This can result in a subsequent call to napi_get_frags returning a dangling pointer.
Fix this by clearing napi->skb before the skb is freed.
From the CVE record · Linux
In the Linux kernel's gve driver, gve_rx_free_skb leaves napi->skb pointing to a freed buffer, so a later napi_get_frags call can return a dangling pointer. The input does not establish what an attacker could do with this or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernel versions with the affected gve code should check their systems; affected versions are not specified.