svcrdma: Clear sc_cm_id when ADDR_CHANGE replacement fails
CVE-2026-89534 · published 11 Sept 2026
How serious is it
- Severity: high, CVSS score 8.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-89534?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: d1b586e75ec619dde1af47e21a41a6b1b51874c2 to < 2a68aeb2de8ad0fef9c50e73a50622a35c6af1a8, d1b586e75ec619dde1af47e21a41a6b1b51874c2 to < 65f0f82f20334e76acaf29087a59af7b3b9699ed, d1b586e75ec619dde1af47e21a41a6b1b51874c2 to < 673e358ab7c11f8cec223c6a36a793056a67facd, d1b586e75ec619dde1af47e21a41a6b1b51874c2 to < 01500306e1d50de7ca7a2cdcdfa28ac0523eb747
- Linux Linux: 6.11
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
svcrdma: Clear sc_cm_id when ADDR_CHANGE replacement fails
When svc_rdma_listen_handler() handles RDMA_CM_EVENT_ADDR_CHANGE,
it creates a replacement listener cm_id and returns 1, telling
the CM core to destroy the old one. If the replacement allocation
fails, sc_cm_id still points at the old cm_id that the CM core is
about to destroy. Any subsequent dereference of sc_cm_id --
such as svc_rdma_detach()'s rdma_disconnect() call -- is a
use-after-free.
NULL sc_cm_id on the failure path and guard svc_rdma_detach()'s
rdma_disconnect() call against NULL so that the listener can
be torn down safely when the server shuts down.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/2a68aeb2de8ad0fef9c50e73a50622a35c6af1a8
- git.kernel.org/stable/c/65f0f82f20334e76acaf29087a59af7b3b9699ed
- git.kernel.org/stable/c/673e358ab7c11f8cec223c6a36a793056a67facd
- git.kernel.org/stable/c/01500306e1d50de7ca7a2cdcdfa28ac0523eb747
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON