Kernel warning via device-less RDMA resource registration
Published Sep 17, 2026 · Updated Sep 17, 2026
Linux 5.13 RDMA/cma error handling allows local users to trigger a kernel warning through asynchronous address resolution. The addr_handler() function calls rdma_restrack_add() even after cma_acquire_dev_by_src_ip() fails, passing a resource with a NULL device pointer to res_to_rt(). The path requires failed RDMA device acquisition; the published trace demonstrates a warning, not a crash or data access.
Summary
What happened
Linux 5.13 RDMA/cma error handling allows local users to trigger a kernel warning through asynchronous address resolution. The addr_handler() function calls rdma_restrack_add() even after cma_acquire_dev_by_src_ip() fails, passing a resource with a NULL device pointer to res_to_rt(). The path requires failed RDMA device acquisition; the published trace demonstrates a warning, not a crash or data access.
The record
- CVE
- CVE-2026-90218
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=073fdf539d4c022162db3d77a5afca1710f0de2d
- Affected versionversion=5.10.37 <5.10.270
- Affected versionversion=5.11.21 <5.12
- Affected versionversion=5.12.4 <5.13
- Affected versionversion=5.13
- Affected versionversion=c5ebaca402f5c5bd61ac8316feb2aa3a0be4d4a8 <1d7e55ea64dd15769318ba2e0fe0956db82ba3c3
- Affected versionversion=cb5cd0ea4eb3ce338a593a5331ddb4986ae20faa <2a63cb9ea862ac7d947952b497eef6520853538c
- Affected versionversion=cb5cd0ea4eb3ce338a593a5331ddb4986ae20faa <39e83bb77fc92344cd62a373b311f096d812e548
- Affected versionversion=cb5cd0ea4eb3ce338a593a5331ddb4986ae20faa <544e40805dbb6cfe64916bd4c8b238fec585ac2a
- Affected versionversion=cb5cd0ea4eb3ce338a593a5331ddb4986ae20faa <64a2bd4cfc16c24f0a0e6321a2fd00ffde3e0a5b
- Affected versionversion=cb5cd0ea4eb3ce338a593a5331ddb4986ae20faa <9c80273d663959504957606b9a24fe901ee2a4a1
- Affected versionversion=cb5cd0ea4eb3ce338a593a5331ddb4986ae20faa <c6d1ec4fbe56492bb88987d577f04a5fb6955f26
- Affected versionversion=cb5cd0ea4eb3ce338a593a5331ddb4986ae20faa <f72957e0b31f2962f4c1089a9223f1206aa26983
- Affected versionversion=fa37a461bd6d9ee86e891ba3e4074a450e44c881
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
No sourced classifications are available.
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