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

Unknown severity · Source severity not reportedCVE-2026-92509

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

Answer in brief

CVE-2026-92509 records a Unknown severity vulnerability in RDMA/core: Fix potential use after free in counter_release(). 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	>=99fa331dc8629be55ac7a0cca0dc56492070ddac <5eb0c57a8b568eb08f464861d84d518a2af939ac \|\| >=99fa331dc8629be55ac7a0cca0dc56492070ddac <d5cc211e8c39e46f357d30a092d683e84d560de9 \|\| >=99fa331dc8629be55ac7a0cca0dc56492070ddac <2f0c6705e26ba92c0c6b0b0908a2d3f35a039d5b \|\| >=99fa331dc8629be55ac7a0cca0dc56492070ddac <8c013e3a8d8273da4d47bf1c27f016a3551996f5 \|\| >=99fa331dc8629be55ac7a0cca0dc56492070ddac <64c72390d8407ea86de712a477c796b07d37abc4 \|\| >=99fa331dc8629be55ac7a0cca0dc56492070ddac <235ef2d0e750885c29340b0fc40620a7a4f52e12	5eb0c57a8b568eb08f464861d84d518a2af939ac, d5cc211e8c39e46f357d30a092d683e84d560de9, 2f0c6705e26ba92c0c6b0b0908a2d3f35a039d5b, 8c013e3a8d8273da4d47bf1c27f016a3551996f5, 64c72390d8407ea86de712a477c796b07d37abc4, 235ef2d0e750885c29340b0fc40620a7a4f52e12
Linux/Linuxgeneric	5.3	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 5eb0c57a8b568eb08f464861d84d518a2af939ac 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 counter_release() When accessing a counter via the netlink path the only synchronization mechanism for the said counter is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of counter_release(), which is too late, since by that point vendor-specific resources associated with the counter might already be freed. This can leave a short window where the counter 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 counter is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a counter that is in the process of destruction.

Quoted source text, attributed separately from HOL analysis.