Linux kernel vulnerability affecting SUNRPC/TLS; widely deployed and can crash or permit kernel-level compromise—high-impact for enterprise infrastructure.
CVE-2026-72317
Linux kernel SUNRPC TLS use-after-free enabling kernel crash or privilege escalation
Is CVE-2026-72317 being exploited?
Not confirmed. CVE-2026-72317 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.64% probability of exploitation in the next 30 days.
How severe is CVE-2026-72317?
CVE-2026-72317 is rated Critical. 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-72317?
Yes. A fix has been recorded for CVE-2026-72317. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72317 affect?
CVE-2026-72317 affects Linux kernel (SUNRPC TLS/xs_tcp_tls_setup_socket), NFS over TLS clients/servers, Linux distributions with affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72317?
Install vendor kernel updates immediately; restrict untrusted NFS/TLS mounts
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free in SUNRPC TLS connect_worker can crash the kernel (DoS) or enable kernel-level compromise/privilege escalation; may be triggered by malicious NFS/TLS servers.
Patch when possible
- affected>= 75eb6af7acdf566c68d61e98e67ee2f235201c02 and < 79cd550f8c884523b604fbfa43eb02def74d6224
- affected>= 75eb6af7acdf566c68d61e98e67ee2f235201c02 and < 7a65b41b657b71d5a77861f47dd13eb4bc8e10d0
- affected>= 75eb6af7acdf566c68d61e98e67ee2f235201c02 and < 5b0427ba582d143a364301f825f4e32272f06d2d
- affected>= 75eb6af7acdf566c68d61e98e67ee2f235201c02 and < d49f6d098ed48775b9d27a9f9c5c220fdf76f102
- affected>= 75eb6af7acdf566c68d61e98e67ee2f235201c02 and < 46bc86c833956219bbfd246c1ffd832a479c5199
- affected6.5
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.