CVE-2026-90415 — RDMA/cxgb4: free STAG index when TPT entry write fails
In the Linux kernel, the following vulnerability has been resolved: RDMA/cxgb4: free STAG index when TPT entry write fails write_tpt_entry() allocates a new STAG index with c4iw_get_resource() and bumps stats.stag.cur before programming the entry. When write_adapter_mem() fails, it returns the error without releasing the index or reversing the statistic. No MR is inserted into rhp->mrs, so deregistration never reclaims it, leaking the index until device teardown. Record whether this call allocated the index and, on a failed write, return it to tpt_table and decrement stats.stag.cur. Key the rollback on both the write error and that flag, not the error alone: a non-reset update carries a caller-owned STAG that this call did not allocate and must not free.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ ec3eead217181d7360a11317a888ceb30807867c and < 5fe4731bfbd8d83c4a14b4af3a27329969ce8a99≥ ec3eead217181d7360a11317a888ceb30807867c and < 8f6976d635d190e3d7af7103daaa581cf1ccc12e≥ ec3eead217181d7360a11317a888ceb30807867c and < 9eeafcda1d6c11f0eec532243c4e96ec8c632bd7≥ ec3eead217181d7360a11317a888ceb30807867c and < 5a21e5114cec4cd3f8a2843d4c46bc49634d6e96≥ ec3eead217181d7360a11317a888ceb30807867c and < 2f17ca7ab5269ac2504e1039c3921373dccd7712≥ ec3eead217181d7360a11317a888ceb30807867c and < a2e37d1ab773be3cd26b1c19593ca2dbcece9c57≥ ec3eead217181d7360a11317a888ceb30807867c and < a64e2beb450179a5d43034af8d5476a11eac1486≥ ec3eead217181d7360a11317a888ceb30807867c and < fdfb5cea4bf070cdb31d997efd87bb684df041fd and 1 moreversion 3.5 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/8f6976d635d190e3d7af7103daaa581cf1ccc12e
- git.kernel.org/stable/c/2f17ca7ab5269ac2504e1039c3921373dccd7712
- git.kernel.org/stable/c/9eeafcda1d6c11f0eec532243c4e96ec8c632bd7
- git.kernel.org/stable/c/5a21e5114cec4cd3f8a2843d4c46bc49634d6e96
- git.kernel.org/stable/c/fdfb5cea4bf070cdb31d997efd87bb684df041fd
- git.kernel.org/stable/c/a2e37d1ab773be3cd26b1c19593ca2dbcece9c57
- git.kernel.org/stable/c/a64e2beb450179a5d43034af8d5476a11eac1486
- git.kernel.org/stable/c/5fe4731bfbd8d83c4a14b4af3a27329969ce8a99
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 5h
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 5h
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 5h
- Unknown CVE-2026-98860 HID: bpf: cast size to ssize_t when checking hid_bpf_hw_request 5h
- Unknown CVE-2026-98865 sched_ext: Don't run ops.dequeue() with a DSQ lock held 5h
- Unknown CVE-2026-98864 sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing a task 5h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90415 is "RDMA/cxgb4: free STAG index when TPT entry write fails", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.