Bug 2536482 (CVE-2026-92509) - CVE-2026-92509 kernel: RDMA/core: Fix potential use after free in counter_release()
Summary: CVE-2026-92509 kernel: RDMA/core: Fix potential use after free in counter_rel...
Keywords:
Status: NEW
Alias: CVE-2026-92509
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 18:10 UTC by OSIDB Bzimport
Modified: 2026-10-20 11:22 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 18:10:17 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.