CVE-2026-99055: tcp: reject net_iov in zerocopy receive mapping hints
In the Linux kernel, the following vulnerability has been resolved:
tcp: reject netiov in zerocopy receive mapping hints
After copying a readable prefix, receivefallbacktocopy() asks tcpzerocopysethintforskb() where page mapping can resume. If the next skb is unreadable, findnextmappablefrag() passes its netiov fragment to canmapfrag().
skbfragpage() returns NULL for a netiov, but canmapfrag() dereferences it in PageCompound(). A v7.2 KASAN run on a connected TCP socket with 64 readable bytes followed by a 4096-byte NETIOVDMABUF fragment reported:
BUG: KASAN: null-ptr-deref in canmapfrag tcpzerocopyreceive -> canmapfrag Kernel panic - not syncing: KASAN: paniconwarn set
The diagnostic inserted the netiov directly because the test host has no devmem-capable NIC. Hardware end-to-end reachability remains untested and requires CONFIGNETDEVMEM plus a supported DMA-buf-bound RX queue.
Reject all netiov fragments before skbfragpage(). This covers both DMABUF and IOURING netiov types while leaving page-backed checks unchanged. With the guard, the same queue copied the readable prefix, returned a 4096-byte skip hint, and completed without a fault.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
azurelinux/kernelto a version that resolves this vulnerability.Fixed in 0:6.18.57-1.1.azl4 - Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.18~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1019.19~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.19~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-43.43~24.04.1 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.18~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-43.43.1~24.04.2 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.3.0-10.10 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.3.0-1004.5 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.3.0-1004.4 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.3.0-10.10.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-43.43 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1017.18 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1020.21 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1019.19 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1017.19 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1010.11 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1018.18 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1018.18 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 7.0.0-1023.23 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-43.43.1
Event History
Frequently Asked Questions
Which systems are realistically exposed to the hardware receive path involved here?
Hardware end-to-end exposure requires CONFIG_NET_DEVMEM and a supported DMA-buf-bound RX queue. The reported test host did not have a devmem-capable NIC, so hardware reachability was not established there.
What conditions trigger the fault?
The failure occurs when zerocopy receive processing copies a readable prefix and then encounters an unreadable skb containing a net_iov fragment. The reported reproducer used a connected TCP socket with 64 readable bytes followed by a 4096-byte NET_IOV_DMABUF fragment.
How can an affected system be recognized?
The reported symptom is a KASAN null-pointer dereference in can_map_frag through tcp_zerocopy_receive, potentially followed by a kernel panic when panic_on_warn is set. The stack results from skb_frag_page() returning NULL for a net_iov fragment before can_map_frag() calls PageCompound().
What is the immediate remediation if the issue is present?
Apply a fix that rejects net_iov fragments before skb_frag_page() is reached. The described guard covers both DMABUF and IOURING net_iov types while retaining existing checks for page-backed fragments.