CVE-2026-92510: Linux Vulnerability

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.

Affected Software

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

Vendor	Product	Versions
Linux	Linux	>= 48f8a70e899fa4d9c8f00369f482f0382173ece9, < a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9; >= 48f8a70e899fa4d9c8f00369f482f0382173ece9, < d3d0eabe6e39b024deb3e085e2d408d037e967c3; >= 48f8a70e899fa4d9c8f00369f482f0382173ece9, < 9c704383529044c02122f85a2a9a42cbf14a07a6; >= 48f8a70e899fa4d9c8f00369f482f0382173ece9, < bedd7dee72588c838f5b67197ea8b387e7beb918; >= 48f8a70e899fa4d9c8f00369f482f0382173ece9, < 95c992c869df54a6a7061f5f3fb6400244f2af8f; >= 48f8a70e899fa4d9c8f00369f482f0382173ece9, < 88244ecc71cc0b3ed200f5ef7ddea6686adfd730
Linux	Linux	5.13

References

Timeline

Published: Sep 17, 2026
Last Modified: Sep 17, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-92510?

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.

How severe is CVE-2026-92510?

Severity scoring for CVE-2026-92510 is pending analysis.

How do I fix CVE-2026-92510?

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 →