CVE-2026-92510RDMA/core: Fix potential use after free in ib_destroy_srq_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_srq_user() When accessing a SRQ via the netlink path the only synchronization mechanism for the said SRQ is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of ib_destroy_srq_user(), which is too late, since by that point vendor-specific resources associated with the SRQ might already be freed. This can leave a short window where the SRQ 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_srq_user(), ensuring that the SRQ is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a SRQ 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 (13 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 48f8a70e899fa4d9c8f00369f482f0382173ece9 – < a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9
- affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 – < d3d0eabe6e39b024deb3e085e2d408d037e967c3
- affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 – < 9c704383529044c02122f85a2a9a42cbf14a07a6
- affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 – < bedd7dee72588c838f5b67197ea8b387e7beb918
- affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 – < 95c992c869df54a6a7061f5f3fb6400244f2af8f
- affected 48f8a70e899fa4d9c8f00369f482f0382173ece9 – < 88244ecc71cc0b3ed200f5ef7ddea6686adfd730
- affected 5.13
- unaffected < 5.13
- 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/a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9 (opens in a new tab)
- https://git.kernel.org/stable/c/d3d0eabe6e39b024deb3e085e2d408d037e967c3 (opens in a new tab)
- https://git.kernel.org/stable/c/9c704383529044c02122f85a2a9a42cbf14a07a6 (opens in a new tab)
- https://git.kernel.org/stable/c/bedd7dee72588c838f5b67197ea8b387e7beb918 (opens in a new tab)
- https://git.kernel.org/stable/c/95c992c869df54a6a7061f5f3fb6400244f2af8f (opens in a new tab)
- https://git.kernel.org/stable/c/88244ecc71cc0b3ed200f5ef7ddea6686adfd730 (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-82131 (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-92510)Record last updated .