RDMA/core: Fix potential use after free in ib_destroy_srq_user() (CVE-2026-92510) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-92510

RDMA/core: Fix potential use after free in ib_destroy_srq_user()

Answer in brief

CVE-2026-92510 records a Unknown severity 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.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
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

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.