linux: In the Linux kernel, the following vulnerability has been resolved: svcrdma: Use svc_xprt_put to free listener on cr...
CVE-2026-89527 is fixed in 15 products on 1 platform, first by DEBIAN-CVE-2026-89527, released September 23, 2026. It is not reported as exploited. Patch Radar priority: Routine.
In the Linux kernel, the following vulnerability has been resolved: svcrdma: Use svc_xprt_put to free listener on create failure svc_rdma_create() calls kfree(cma_xprt) when svc_rdma_create_listen_id() fails. svc_xprt_init() has already acquired a net namespace reference via get_net_track(); kfree bypasses svc_xprt_free() which releases it. Replace the kfree() with svc_xprt_put() so the kref_init birth reference drops to zero and svc_xprt_free() dispatches svc_rdma_free() to clean up properly. sc_cm_id is still NULL at that point; the preceding patch added the necessary NULL guard in svc_rdma_free(). svc_xprt_free() also drops the module reference via module_put(), but the caller _svc_xprt_create() does the same on xpo_create failure, double-putting the single try_module_get() it acquired. Take a compensating __module_get() before the svc_xprt_put() to keep the count balanced, matching the convention in svc_rdma_accept()'s error path.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| dtb-aarch64 · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-64kb · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-64kb · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| kernel-azure · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-azure · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| kernel-default · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-default · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24197-1 | Nov 7, 2026 |
| kernel-default-base · opensuse-leap 16.0 | 6.12.0-160000.39.1.160000.2.25 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-default-base · sles 16.0 | 6.12.0-160000.39.1.160000.2.26 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| kernel-docs · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-docs · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| kernel-kvmsmall · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-kvmsmall · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| kernel-obs-build · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-obs-qa · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-obs-qa · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| kernel-rt · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-source · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-source · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| kernel-syms · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-syms · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| kernel-zfcpdump · opensuse-leap 16.0 | 6.12.0-160000.39.1 | OPENSUSE-SU-2026:22091-1 | Nov 7, 2026 |
| kernel-zfcpdump · sles 16.0 | 6.12.0-160000.39.1 | SUSE-SU-2026:24235-1 | Nov 7, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.113-1 | DEBIAN-CVE-2026-89527 | Sep 23, 2026 |
| linux · Debian 14 | 7.2.6-1 | DEBIAN-CVE-2026-89527 | Sep 23, 2026 |
| linux-6.12 · Debian 12.15 (bookworm) | 6.12.113-1~deb12u1 | DEBIAN-CVE-2026-89527 | Sep 23, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.