xfrm: hold dev ref until after transport_finish NF_HOOK
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ acf568ee859f098279eadf551612f103afdacb4e · < 1c428b03840094410c5fb6a5db30640486bbbfcb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xfrm: hold dev ref until after transport_finish NF_HOOK
After async crypto completes, xfrm_input_resume() calls dev_put() immediately on re-entry before the skb reaches transport_finish. The skb->dev pointer is then used inside NF_HOOK and its okfn, which can race with device teardown.
Remove the dev_put from the async resumption entry and instead drop the reference after the NF_HOOK call in transport_finish, using a saved device pointer since NF_HOOK may consume the skb. This covers NF_DROP, NF_QUEUE and NF_STOLEN paths that skip the okfn.
For non-transport exits (decaps, gro, drop) and secondary async return points, release the reference inline when async is set.
From the CVE record · Linux
The Linux kernel's xfrm path can release a device reference before NF_HOOK finishes using the device pointer. After asynchronous crypto completes, this can race with device teardown and cause a use-after-free. The input does not specify attacker access requirements or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.