svcrdma: Reject connection when transport allocation fails
Summary
| CVE | CVE-2026-89531 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-11 20:19:35 UTC |
| Updated | 2026-09-11 20:19:35 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: svcrdma: Reject connection when transport allocation fails handle_connect_req() returns without action when svc_rdma_create_xprt() fails to allocate the new transport. The CM core returns 0 for CONNECT_REQUEST events, so it does not destroy the new rdma_cm_id. Each allocation failure under memory pressure leaks one rdma_cm_id, and a remote peer driving connection attempts can amplify this. Reject the connection by returning a non-zero status from the CM event handler, which tells the CM core to destroy the orphaned cm_id. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.063420000 (date 2026-09-13)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 377f9b2f4529e0ac702fd7b91e216afd0adc959e 6e21754bbf75075f3fee1cebc79f3417364235ec git | Not specified |
| CNA | Linux | Linux | affected 377f9b2f4529e0ac702fd7b91e216afd0adc959e 3cf372cec7ab2cd8c6002bf775cc14d90ccb098b git | Not specified |
| CNA | Linux | Linux | affected 377f9b2f4529e0ac702fd7b91e216afd0adc959e 1f6a14c142fee4778c32709d1d54595c2e2b7991 git | Not specified |
| CNA | Linux | Linux | affected 377f9b2f4529e0ac702fd7b91e216afd0adc959e 0944462247dcb7de7622cdaaadf5f05c52707dab git | Not specified |
| CNA | Linux | Linux | affected 2.6.25 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.25 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.109 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.50 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.4 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/6e21754bbf75075f3fee1cebc79f3417364235ec | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/1f6a14c142fee4778c32709d1d54595c2e2b7991 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3cf372cec7ab2cd8c6002bf775cc14d90ccb098b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0944462247dcb7de7622cdaaadf5f05c52707dab | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.