net-shapers: don't free reply skb after genlmsg_reply()
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.196.19.97.0In the Linux kernel, the following vulnerability has been resolved:
net-shapers: don't free reply skb after genlmsg_reply()
genlmsg_reply() hands the reply skb to netlink, and netlink_unicast() consumes it on all return paths, whether the skb is queued successfully or freed on an error path.
net_shaper_nl_get_doit() and net_shaper_nl_cap_get_doit() currently jump to free_msg after genlmsg_reply() fails and call nlmsg_free(msg), which can hit the same skb twice.
Return the genlmsg_reply() error directly and keep free_msg only for pre-reply failures.
From the CVE record · Linux
The Linux kernel’s net-shapers reply handlers can free the same network buffer twice when genlmsg_reply() fails. The input does not establish whether an attacker can trigger that failure, or specify access or user-interaction requirements.
Engineers running Linux kernels with the affected net-shapers code should check their kernel versions against the vendor advisory; affected versions were not provided.