Skip to content
major vulnerability· requires attention

Linux kernel TLS vulnerability affects widely deployed kernels; remote TLS peers can trigger memory corruption across servers and networked devices, posing broad infrastructure risk.

Systems

CVE-2026-74611

9.8
Critical
EPSS 0.44%Patch availableAug 25, 2026

Linux kernel TLS 1.3 zero-copy bug allows recvmsg() buffer overwrite by peer.

common questions

Is CVE-2026-74611 being exploited?

Not confirmed. CVE-2026-74611 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.

How severe is CVE-2026-74611?

CVE-2026-74611 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74611?

Yes. A fix has been recorded for CVE-2026-74611. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74611 affect?

CVE-2026-74611 affects Linux kernel (TLS subsystem), Kernels with TLS 1.3 zero-copy and TLS_RX_EXPECT_NO_PAD enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74611?

Install kernel security updates ASAP; block untrusted TLS peers or disable zero-copy TLS RX until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (TLS subsystem)Kernels with TLS 1.3 zero-copy and TLS_RX_EXPECT_NO_PAD enabled
impact

A remote TLS peer can cause recvmsg() to overwrite later user iovecs, leading to memory corruption, data overwrite, DoS or potential code execution.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= ce61327ce989b63c0bd1cc7afee00e218ee696ac and < 68787940274ec89f41dc91b1a68ee1a16a90735f
  • affected>= ce61327ce989b63c0bd1cc7afee00e218ee696ac and < 3c837266a734e2a22b24d2d567404a501d405835
  • affected>= ce61327ce989b63c0bd1cc7afee00e218ee696ac and < 1c8629651cb54f7b51db8fc0b1a9944e4a4b0f5e
  • affected6.0
vendor says fixed in< 6.0, >= 6.18.45 and <= 6.18.*, >= 7.1.9 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free