Strix
63.2K

CVE-2026-92509

Unknown

Last modified

CVE-2026-92509 is a vulnerability of currently unknown severity. 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..

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 5eb0c57a8b568eb08f464861d84d518a2af939ac; >= 99fa331dc8629be55ac7a0cca0dc56492070ddac, < d5cc211e8c39e46f357d30a092d683e84d560de9; >= 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 2f0c6705e26ba92c0c6b0b0908a2d3f35a039d5b; >= 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 8c013e3a8d8273da4d47bf1c27f016a3551996f5; >= 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 64c72390d8407ea86de712a477c796b07d37abc4; >= 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 235ef2d0e750885c29340b0fc40620a7a4f52e12
LinuxLinux5.3

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-92509?
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.
How severe is CVE-2026-92509?
Severity scoring for CVE-2026-92509 is pending analysis.
How do I fix CVE-2026-92509?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-92509?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST