CVE-2026-68288

net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD

N/A
Published: August 10, 2026 at 12:02 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4 ≤ v < 6.1.1895.4 ≤ v < 6.12.1115.4 ≤ v < 6.18.535.4 ≤ v < 6.6.1585.4 ≤ v < 7.1.65.4 ≤ v < 7.25.4ca30707dee2bc8bc81cfd8b4277fe90f7ca6df1f
Vendor states this is fixed in 05173de42a9923a3eaadebcb0dd5bc83ffba174c (fixed)
Vendor states this is fixed in 3c0bc7dcc5f9257d25c59eeb7ccb4df33dcfc446 (fixed)
Vendor states this is fixed in 5e9c8baee0329fbefe7c67aea945e2a07f15e98b (fixed)
Vendor states this is fixed in 89178ffe5bddc99c057ba2768db1f8d9c5e1408c (fixed)
Vendor states this is fixed in 8fd6975d2aecc36b25ee82b6aef88e62a3527ccb (fixed)
Vendor states this is fixed in d427b152b663cb2b19fcd449d792e17edbe4a938 (fixed)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card