Resource exhaustion via failed-write STAG index leak
Published Sep 17, 2026 · Updated Sep 17, 2026
Resource leakage in Linux RDMA/cxgb4 allows local users to exhaust STAG indices through failed adapter-memory writes. The write_tpt_entry() function allocates an index but does not release it when write_adapter_mem() fails; no memory region is registered for deregistration to reclaim it. Exposure requires the cxgb4 RDMA driver and failed adapter writes; leaked indices persist until device teardown and prevent further allocations when the pool is exhausted.
Summary
What happened
Resource leakage in Linux RDMA/cxgb4 allows local users to exhaust STAG indices through failed adapter-memory writes. The write_tpt_entry() function allocates an index but does not release it when write_adapter_mem() fails; no memory region is registered for deregistration to reclaim it. Exposure requires the cxgb4 RDMA driver and failed adapter writes; leaked indices persist until device teardown and prevent further allocations when the pool is exhausted.
The record
- CVE
- CVE-2026-90415
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-772
- 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=3.5
- Affected versionversion=ec3eead217181d7360a11317a888ceb30807867c <2f17ca7ab5269ac2504e1039c3921373dccd7712
- Affected versionversion=ec3eead217181d7360a11317a888ceb30807867c <5a21e5114cec4cd3f8a2843d4c46bc49634d6e96
- Affected versionversion=ec3eead217181d7360a11317a888ceb30807867c <5fe4731bfbd8d83c4a14b4af3a27329969ce8a99
- Affected versionversion=ec3eead217181d7360a11317a888ceb30807867c <8f6976d635d190e3d7af7103daaa581cf1ccc12e
- Affected versionversion=ec3eead217181d7360a11317a888ceb30807867c <9eeafcda1d6c11f0eec532243c4e96ec8c632bd7
- Affected versionversion=ec3eead217181d7360a11317a888ceb30807867c <a2e37d1ab773be3cd26b1c19593ca2dbcece9c57
- Affected versionversion=ec3eead217181d7360a11317a888ceb30807867c <a64e2beb450179a5d43034af8d5476a11eac1486
- Affected versionversion=ec3eead217181d7360a11317a888ceb30807867c <fdfb5cea4bf070cdb31d997efd87bb684df041fd
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
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