net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ca30707dee2bc8bc81cfd8b4277fe90f7ca6df1f · < 5e9c8baee0329fbefe7c67aea945e2a07f15e98b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD
net_dm_packet_report_fill() and net_dm_hw_packet_report_fill() open code the NET_DM_ATTR_PAYLOAD attribute to avoid zeroing the packet payload before overwriting it with skb_copy_bits().
skb_put() reserves nla_total_size(payload_len), i.e. the header plus the NLA_ALIGN() padding, but only payload_len bytes are copied in. When payload_len is not a multiple of 4 the 1-3 padding bytes are never initialized and are leaked to user space inside the netlink message.
KMSAN confirms the leak for the software path when the packet payload length is not 4-byte aligned:
BUG: KMSAN: kernel-infoleak in _copy_to_iter _copy_to_iter __skb_datagram_iter skb_copy_datagram_iter netlink_recvmsg sock_recvmsg __sys_recvfrom Uninit was created at: kmem_cache_alloc_node_noprof __alloc_skb net_dm_packet_work Bytes 173-175 of 176 are uninitialized
Use __nla_reserve(), which sets up the attribute header and zeroes the padding, instead of open coding the attribute construction.
From the CVE record · Linux
The Linux kernel's drop_monitor can leave 1–3 padding bytes uninitialized in NET_DM_ATTR_PAYLOAD netlink messages when a packet payload length is not divisible by four. A local recipient of such a message can receive leaked kernel data; the input does not specify authentication requirements or any user interaction.
Teams running the Linux kernel should check whether their kernel includes the affected drop_monitor code; affected versions are not specified.