CVE-2026-92511RDMA/core: Fix potential use after free in ib_destroy_cq_user()
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in ib_destroy_cq_user() 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_destroy_cq_user(), 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_begin_del() call to the start of ib_destroy_cq_user(), 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. In addition, this change preserves the intended inverted order between create and destroy routines: resources are added to restrack at the end of successful creation, and hence shall be removed from the restrack first thing during the destruction flow, which keeps the lifecycle management consistent and predictable.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 08f294a1524bc3211a28091daa6c7513828c7d33 – < 42f7a0c7a94003059540cce448acabfa62ad119d
- affected 08f294a1524bc3211a28091daa6c7513828c7d33 – < 253c2ed71a532c70fa0e64317ceb02bb1a50c84c
- affected 08f294a1524bc3211a28091daa6c7513828c7d33 – < b85a148731eceffacb6a030950187d785175607f
- affected 08f294a1524bc3211a28091daa6c7513828c7d33 – < 197c262dbf94c0f7ab7ac54b66f892ce9f343232
- affected 08f294a1524bc3211a28091daa6c7513828c7d33 – < 8a72a6aad84b3928dbb5e564bff1f56a7ec222ae
- affected 08f294a1524bc3211a28091daa6c7513828c7d33 – < 3481bec4dfc4aee24ffea5a547ee95b70b67d9d5
- affected 4.16
- unaffected < 4.16
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/42f7a0c7a94003059540cce448acabfa62ad119d (opens in a new tab)
- https://git.kernel.org/stable/c/253c2ed71a532c70fa0e64317ceb02bb1a50c84c (opens in a new tab)
- https://git.kernel.org/stable/c/b85a148731eceffacb6a030950187d785175607f (opens in a new tab)
- https://git.kernel.org/stable/c/197c262dbf94c0f7ab7ac54b66f892ce9f343232 (opens in a new tab)
- https://git.kernel.org/stable/c/8a72a6aad84b3928dbb5e564bff1f56a7ec222ae (opens in a new tab)
- https://git.kernel.org/stable/c/3481bec4dfc4aee24ffea5a547ee95b70b67d9d5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82132 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-92511)Record last updated .