Kernel resource leak via failed RDMA accepts
Published Sep 24, 2026 · Updated Sep 24, 2026
Resource-management errors in the Linux svcrdma transport allow attackers to leak kernel resources through failed RPC-over-RDMA accepts. When svc_rdma_accept() exits before registration succeeds, cleanup unconditionally unregisters a zero-initialized entry, erases another caller's slot, drops an unmatched device reference, and fails to release the new transport. Reachability requires an RPC-over-RDMA service and an accept failure before registration; each failed accept pins the transport and its network namespace, while the unmatched unregister can corrupt shared device bookkeeping.
Summary
What happened
Resource-management errors in the Linux svcrdma transport allow attackers to leak kernel resources through failed RPC-over-RDMA accepts. When svc_rdma_accept() exits before registration succeeds, cleanup unconditionally unregisters a zero-initialized entry, erases another caller's slot, drops an unmatched device reference, and fails to release the new transport. Reachability requires an RPC-over-RDMA service and an accept failure before registration; each failed accept pins the transport and its network namespace, while the unmatched unregister can corrupt shared device bookkeeping.
The record
- CVE
- CVE-2026-93224
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.12.35 <6.12.109
- Affected versionversion=6.15.4 <6.16
- Affected versionversion=6.16
- Affected versionversion=8ac6fcae5dc0e801f1c82a83f5ae2c0a4db19932 <26190394c64c9429481fc88a4738f70bb92fb352
- Affected versionversion=8ac6fcae5dc0e801f1c82a83f5ae2c0a4db19932 <45a444a17240f4fa2235f0dfd4a96fc80f1eb2c2
- Affected versionversion=8ac6fcae5dc0e801f1c82a83f5ae2c0a4db19932 <5aabe070c00e5bdf4ab150fb5f72ad5f266d6241
- Affected versionversion=cb3cba0ec372fa7c5f5f5c12990bef02e458ab86 <0335800071a6dfdf7d21d729b5e7d8fa98936211
- Affected versionversion=d310955106c358c8e1ea682defd8e21af44a6cba
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started