Answer in brief
CVE-2026-92510 records a High severity (CVSS 7.8) vulnerability in RDMA/core: Fix potential use after free in ib_destroy_srq_user(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=48f8a70e899fa4d9c8f00369f482f0382173ece9 <a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9 || >=48f8a70e899fa4d9c8f00369f482f0382173ece9 <d3d0eabe6e39b024deb3e085e2d408d037e967c3 || >=48f8a70e899fa4d9c8f00369f482f0382173ece9 <9c704383529044c02122f85a2a9a42cbf14a07a6 || >=48f8a70e899fa4d9c8f00369f482f0382173ece9 <bedd7dee72588c838f5b67197ea8b387e7beb918 || >=48f8a70e899fa4d9c8f00369f482f0382173ece9 <95c992c869df54a6a7061f5f3fb6400244f2af8f || >=48f8a70e899fa4d9c8f00369f482f0382173ece9 <88244ecc71cc0b3ed200f5ef7ddea6686adfd730 | a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9, d3d0eabe6e39b024deb3e085e2d408d037e967c3, 9c704383529044c02122f85a2a9a42cbf14a07a6, bedd7dee72588c838f5b67197ea8b387e7beb918, 95c992c869df54a6a7061f5f3fb6400244f2af8f, 88244ecc71cc0b3ed200f5ef7ddea6686adfd730 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.