tls: rx: restore msg_iter before TLS 1.3 optimistic retry
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ce61327ce989b63c0bd1cc7afee00e218ee696ac · < 1c8629651cb54f7b51db8fc0b1a9944e4a4b0f5e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tls: rx: restore msg_iter before TLS 1.3 optimistic retry
tls_decrypt_sg() advances msg->msg_iter when it maps user pages for the optimistic TLS 1.3 zero-copy path. If the decrypted record turns out not to be unpadded application data, tls_decrypt_sw() retries into a kernel skb, but leaves the iterator advanced.
The subsequent copy from the skb then writes decrypted bytes again at a later point in the caller iovecs while recvmsg() reports only the post-retry length. A TLS peer can trigger this after the receiver enables TLS_RX_EXPECT_NO_PAD.
Revert the iterator by the number of bytes consumed by the optimistic mapping before retrying without zero-copy.
Add a selftest which sends a TLS 1.3 control record with TLS_RX_EXPECT_NO_PAD enabled and verifies that recvmsg() does not overwrite later iovecs beyond the returned length.
From the CVE record · Linux
The Linux kernel TLS receive path can leave a caller's iterator advanced when an optimistic TLS 1.3 zero-copy decrypt falls back to a kernel buffer. A remote TLS peer can trigger a subsequent copy that overwrites later caller iovecs beyond the length reported by recvmsg(), if the receiver has enabled TLS_RX_EXPECT_NO_PAD. No authentication or user interaction requirements are specified.
Operators of Linux systems using the kernel TLS receive path should check their kernel; affected versions are not specified.