CVE-2026-92511: RDMA/core: Fix potential use after free in ib_destroy_cq_user()

Published Sep 17, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

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

When accessing a CQ via the netlink path the only synchronization mechanism for the said CQ is rdmarestrackget(). Currently, rdmarestrackdel() is invoked at the end of ibdestroycquser(), which is too late, since by that point vendor-specific resources associated with the CQ might already be freed. This can leave a short window where the CQ remains accessible through restrack, leading to a potential use-after-free.

Fix this by moving the rdmarestrackbegindel() call to the start of ibdestroycquser(), ensuring that the CQ is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a CQ 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

1 affected component
Linux Kernel

Event History

Sep 17, 2026
CVE Published
via MITRE·04:10 PM
Data Sourced
via MITRE·04:10 PM
Description

Frequently Asked Questions

1

Which systems are most relevant for triage?

Systems using Linux kernel RDMA completion queues and accessing those queues through the netlink path are relevant. The issue requires a CQ to be undergoing destruction while it remains reachable through RDMA resource tracking.

2

What condition creates the exposure window?

The exposure exists when vendor-specific CQ resources have begun to be freed but the CQ has not yet been removed from restrack. During that interval, a new netlink-path user may obtain a reference to the CQ and access freed resources.

3

What does the fix change operationally?

The fix removes the CQ from restrack at the start of the user CQ destruction flow, before its internal resources are released. This prevents new references from being acquired for a CQ that is being destroyed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203