CVE-2026-90292: RDMA/siw: Fix use-after-free in siw_accept()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 561651d6a15588cee2040755f253faca2463415c, 59de5502f32895ffe9c45530327ed997b90fdf06, 8f286a8094ee32c415f9ecd2c20765beb8a18c79; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 561651d6a15588cee2040755f253faca2463415c, 59de5502f32895ffe9c45530327ed997b90fdf06, 8f286a8094ee32c415f9ecd2c20765beb8a18c79; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix use-after-free in siw_accept() siw_accept() looks up the QP supplied by userspace. If that QP is already in RTS, the function jumps to error cleanup before associating the incoming CEP with it. The cleanup tests whether qp->cep is non-NULL and assumes the current call installed the association. However, qp->cep can point to the CEP of an existing connection. The cleanup then drops a reference from the incoming cep, not qp->cep. Once the incoming endpoint loses its remaining references, this can free it before the subsequent cep->qp store, causing a use-after-free. It also clears the existing QP association. Only release the association reference when qp->cep is the incoming CEP. This preserves an existing association and avoids accessing the freed endpoint.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.3affected
- 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and later · before d57db36e74cca4763e1c2c0c6eb9f84d19813879affected · git
- 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and later · before 59de5502f32895ffe9c45530327ed997b90fdf06affected · git
- 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and later · before a89d120615e711ce8fce551fd291c2f387666735affected · git
- 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and later · before b9e7d3d9fdb2bfcfb25d93529fdf766536b37c78affected · git
- 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and later · before 8f286a8094ee32c415f9ecd2c20765beb8a18c79affected · git
- 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and later · before de603f01d9ccf823e575b013ffd86ebedca9a8c5affected · git
- 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and later · before 561651d6a15588cee2040755f253faca2463415caffected · git
- 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and later · before a9394971825933074032794a5feee5211509c774affected · git
- before 5.3not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90290Sep 17, 2026 · arm64: hibernate: Restore DAIF state on error0Monitor
- ← EarlierCVE-2026-90291Sep 17, 2026 · module/dups: Fix use-after-free in kmod_dup_req lifetime handling31Monitor
- Later →CVE-2026-90293Sep 17, 2026 · IB/isert: post the full-feature receive buffers after session registration30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 561651d6a15588cee2040755f253faca2463415c | Vendor (CNA) |
| Linux Linux | 59de5502f32895ffe9c45530327ed997b90fdf06 | Vendor (CNA) |
| Linux Linux | 8f286a8094ee32c415f9ecd2c20765beb8a18c79 | Vendor (CNA) |
| Linux Linux | a89d120615e711ce8fce551fd291c2f387666735 | Vendor (CNA) |
| Linux Linux | a9394971825933074032794a5feee5211509c774 | Vendor (CNA) |
| Linux Linux | b9e7d3d9fdb2bfcfb25d93529fdf766536b37c78 | Vendor (CNA) |
| Linux Linux | d57db36e74cca4763e1c2c0c6eb9f84d19813879 | Vendor (CNA) |
| Linux Linux | de603f01d9ccf823e575b013ffd86ebedca9a8c5 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/59de5502f32895ffe9c45530327ed997b90fdf06
- git.kernel.org/stable/c/8f286a8094ee32c415f9ecd2c20765beb8a18c79
- git.kernel.org/stable/c/a89d120615e711ce8fce551fd291c2f387666735
- git.kernel.org/stable/c/a9394971825933074032794a5feee5211509c774
- git.kernel.org/stable/c/b9e7d3d9fdb2bfcfb25d93529fdf766536b37c78
- git.kernel.org/stable/c/d57db36e74cca4763e1c2c0c6eb9f84d19813879
- git.kernel.org/stable/c/de603f01d9ccf823e575b013ffd86ebedca9a8c5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.