CVE-2026-74611
Last modified
CVE-2026-74611 is a vulnerability of currently unknown severity. 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.
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < 68787940274ec89f41dc91b1a68ee1a16a90735f; >= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < 3c837266a734e2a22b24d2d567404a501d405835; >= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < 1c8629651cb54f7b51db8fc0b1a9944e4a4b0f5e |
| Linux | Linux | 6.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74611?
How severe is CVE-2026-74611?
How do I fix CVE-2026-74611?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74606In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74607In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74608In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74609In the Linux kernel, the following vulnerability has been re…
- CVE-2026-7461Improper neutralization of inputs used in an OS command in t…7.5
- CVE-2026-74610In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74612In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74613In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74614In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74615In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74616In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74617In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-74611?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
