net: guard timestamp cmsgs to real error queue skbs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8605330aac5a5785630aec8f64378a54891937cc · < 3dde4fb941fa5649ab809f6cd3e20e0c424a4e31| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: guard timestamp cmsgs to real error queue skbs
skb_is_err_queue() treats PACKET_OUTGOING as the sole marker for an skb from sk_error_queue. That assumption is not true for AF_PACKET sockets: outgoing packet taps are also delivered to packet sockets with skb->pkt_type == PACKET_OUTGOING, but their skb->cb is owned by AF_PACKET instead of struct sock_exterr_skb.
If such an skb is received with timestamping enabled, the generic timestamp cmsg path can read AF_PACKET control-buffer state as sock_exterr_skb::opt_stats. With SO_RXQ_OVFL enabled, the packet drop counter overlaps opt_stats. An odd drop count makes the path emit SCM_TIMESTAMPING_OPT_STATS with skb->len and skb->data. For non-linear skbs this copies past the linear head and can trigger hardened usercopy or disclose adjacent heap contents.
Keep skb_is_err_queue() local to net/socket.c, but make it verify that the PACKET_OUTGOING marker is paired with the sock_rmem_free destructor installed by sock_queue_err_skb(). AF_PACKET receive skbs use normal receive ownership and no longer pass as error-queue skbs, while legitimate sk_error_queue entries keep the PACKET_OUTGOING marker and sock_rmem_free ownership.
From the CVE record · Linux
The Linux kernel can mistake an outgoing packet received by an AF_PACKET socket for an error-queue packet. When timestamping and SO_RXQ_OVFL are enabled, an odd packet-drop count can cause a non-linear packet to trigger a hardened usercopy failure or disclose adjacent heap contents. The described path requires receiving such a packet; the input does not specify authentication requirements.
Engineers running Linux kernels with AF_PACKET sockets that use timestamping and SO_RXQ_OVFL should check their affected versions.