CVE-2026-74611

CRITICALCVSS 9.8/10EPSS 0.46%

Last modified

CVE-2026-74611 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 0.46% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.46%

39.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < 97004f3c17371ee1b259887298711e0604666688; >= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < c71bacacd59166adbea423a04e7474b0e8245b84; >= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < 3c4e21b1bf8e666a1c141e0f5813ece929570deb; >= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < 68787940274ec89f41dc91b1a68ee1a16a90735f; >= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < 3c837266a734e2a22b24d2d567404a501d405835; >= ce61327ce989b63c0bd1cc7afee00e218ee696ac, < 1c8629651cb54f7b51db8fc0b1a9944e4a4b0f5e
LinuxLinux6.0

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74611?
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.
How severe is CVE-2026-74611?
CVE-2026-74611 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 0.46% probability of exploitation in the next 30 days.
How do I fix CVE-2026-74611?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-74611?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST