tcp: reject non zerocopy devmem tx
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.527.2.67.3In the Linux kernel, the following vulnerability has been resolved:
tcp: reject non zerocopy devmem tx
Devmem tcp tx doesn't work without zero-copy, however it's not currently enforced if NETIF_F_SG isn't present. In this case, tcp_sendmsg_locked() will try the copy path and try to copy data from an iovec which consists of offsets into the dma-buf and would normally fail. Moreover, d9c56501c72fd ("net: tcp: block mixing readable and unreadable frags") relies on that and assumes that the devmem binding is present IFF we're using the zero-copy path, which can be used to mix net-iov and pages in a single skb, and break invariants. Let's reject devmem tx without zero-copy.
Note, the parameter check the patch is modifying is too loose, we can create an io_uring request with dmabuf_id and all ZC flags, but which won't have the binding. We replace it with stricter validation.
From the CVE record · Linux
The Linux kernel does not properly reject devmem TCP transmissions that lack zero-copy support, allowing net-iov fragments and pages to be mixed in one packet buffer and breaking internal invariants. This can occur when zero-copy is unavailable, including when NETIF_F_SG is absent; the input does not specify attacker access or authentication requirements.
Engineers running Linux kernels with devmem TCP transmit support should check their kernel versions against the vendor advisory; affected versions are not specified.