CVE-2026-92508: RDMA/core: Fix potential use after free in ib_free_cq()
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 29dc2f8e1c97372c2871a70088707933515fbd5b, 43403fe45379c64fa6276e5a8ede44493e5d2d3d, 5.10; 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 29dc2f8e1c97372c2871a70088707933515fbd5b, 43403fe45379c64fa6276e5a8ede44493e5d2d3d, 5.10; 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/core: Fix potential use after free in ib_free_cq() When accessing a CQ via the netlink path the only synchronization mechanism for the said CQ is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of ib_free_cq(), which is too late, since by that point vendor-specific resources associated with the CQ might already be freed. This can leave a short window where the CQ remains accessible through restrack, leading to a potential use-after-free. Fix this by moving the rdma_restrack_del() call to be before the freeing of the vendor-specific resources ensuring that the CQ is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a CQ that is in the process of destruction.
- 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
- 7ac277a01f9017fcde4f3f81670c995992945433, 093f87dda065e0f618dd577985eccbe85efb9b54, 5.10affected
- 43d781b9fa562f0c6e50f62c870fbfeb9dc85213 and later · before a804b162f9bc2b38b2ed1b4752eea9faadb1645baffected · git
- 43d781b9fa562f0c6e50f62c870fbfeb9dc85213 and later · before 91f8a17a22ab615a03743120e19935e731f28fb9affected · git
- 43d781b9fa562f0c6e50f62c870fbfeb9dc85213 and later · before 76f2cb4f721815c3b6262a6dc2151de88646924caffected · git
- 43d781b9fa562f0c6e50f62c870fbfeb9dc85213 and later · before b8dcca427096fc9c50f1b376847fea72bc842d31affected · git
- 43d781b9fa562f0c6e50f62c870fbfeb9dc85213 and later · before 9abea37942534eeb049335476178696b654b000caffected · git
- 43d781b9fa562f0c6e50f62c870fbfeb9dc85213 and later · before 43403fe45379c64fa6276e5a8ede44493e5d2d3daffected · git
- 43d781b9fa562f0c6e50f62c870fbfeb9dc85213 and later · before 29dc2f8e1c97372c2871a70088707933515fbd5baffected · git
- 5.8.17 and later · before 5.9affected · semver
- 5.9.2 and later · before 5.10affected · 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-92506Sep 17, 2026 · firmware: arm_scmi: Fix requested device removal race0Monitor
- ← EarlierCVE-2026-92507Sep 17, 2026 · RDMA/core: Fix potential use after free in ib_dealloc_pd_user()31Monitor
- Later →CVE-2026-92509Sep 17, 2026 · RDMA/core: Fix potential use after free in counter_release()0Monitor
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 | 29dc2f8e1c97372c2871a70088707933515fbd5b | Vendor (CNA) |
| Linux Linux | 43403fe45379c64fa6276e5a8ede44493e5d2d3d | Vendor (CNA) |
| Linux Linux | 5.10 | Vendor (CNA) |
| Linux Linux | 5.9 | Vendor (CNA) |
| Linux Linux | 76f2cb4f721815c3b6262a6dc2151de88646924c | Vendor (CNA) |
| Linux Linux | 91f8a17a22ab615a03743120e19935e731f28fb9 | Vendor (CNA) |
| Linux Linux | 9abea37942534eeb049335476178696b654b000c | Vendor (CNA) |
| Linux Linux | a804b162f9bc2b38b2ed1b4752eea9faadb1645b | Vendor (CNA) |
| Linux Linux | b8dcca427096fc9c50f1b376847fea72bc842d31 | 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 (6 more)Show less
- git.kernel.org/stable/c/43403fe45379c64fa6276e5a8ede44493e5d2d3d
- git.kernel.org/stable/c/76f2cb4f721815c3b6262a6dc2151de88646924c
- git.kernel.org/stable/c/91f8a17a22ab615a03743120e19935e731f28fb9
- git.kernel.org/stable/c/9abea37942534eeb049335476178696b654b000c
- git.kernel.org/stable/c/a804b162f9bc2b38b2ed1b4752eea9faadb1645b
- git.kernel.org/stable/c/b8dcca427096fc9c50f1b376847fea72bc842d31
Vendor advisories and official records. Exploit/PoC links are deliberately left out.