bpf: Fix use-after-free in offloaded map/prog info fill
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 675fc275a3a2d905535207237402c6d8dcb5fa4b · < 85dc711f742b192eb97c0e00b521312f5a7a415e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix use-after-free in offloaded map/prog info fill
When querying info for an offloaded BPF map or program, bpf_map_offload_info_fill_ns() and bpf_prog_offload_info_fill_ns() obtain the network namespace with get_net(dev_net(offmap->netdev)). However, the associated netdev's netns may be racing with teardown during netns destruction. If the netns refcount has already reached 0, get_net() performs a refcount_t increment on 0, triggering:
refcount_t: addition on 0; use-after-free.
Although rtnl_lock and bpf_devs_lock ensure the netdev pointer remains valid, they cannot prevent the netns refcount from reaching zero.
Fix this by using maybe_get_net() instead of get_net(). maybe_get_net() uses refcount_inc_not_zero() and returns NULL if the refcount is already zero, which causes ns_get_path_cb() to fail and the caller to return -ENOENT -- the correct behavior when the netns is being destroyed.
From the CVE record · Linux
The Linux kernel can trigger a use-after-free when an offloaded BPF map or program info query races with network namespace teardown. The issue involves the network namespace reference count reaching zero; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels that support offloaded BPF maps or programs should check their kernel version against the vendor advisory; affected versions are not specified.