netdev: fix double-free in netdev_nl_bind_rx_doit()
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:
netdev: fix double-free in netdev_nl_bind_rx_doit()
Sashiko flags that genlmsg_reply() always consumes the skb. The error path calls nlmsg_free(rsp) so we can't jump directly to it. Let's not unbind, just propagate the error to the user. This is the typical way of handling genlmsg_reply() failures. They shouldn't happen unless user does something silly like calling the kernel with an already-full rcvbuf.
From the CVE record · Linux
The Linux kernel has a double-free in the error path of netdev_nl_bind_rx_doit(): genlmsg_reply() consumes the response buffer, but the error path can free it again. A local caller can encounter this path if genlmsg_reply() fails, for example when the receive buffer is already full. The input does not specify an authentication requirement or other user interaction.
Teams running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified in the input.