CVE-2026-92510

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

HIGH
7.8
CVSS Score
Published: September 17, 2026 at 04:10 PM UTC
Updated: October 19, 2026 at 10:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

48f8a70e899fa4d9c8f00369f482f0382173ece95.13
Vendor states this is fixed in 88244ecc71cc0b3ed200f5ef7ddea6686adfd730 (fixed)
Vendor states this is fixed in 95c992c869df54a6a7061f5f3fb6400244f2af8f (fixed)
Vendor states this is fixed in 9c704383529044c02122f85a2a9a42cbf14a07a6 (fixed)
Vendor states this is fixed in a5bfd9fe05d5cebbd3e447bf7f7b2c663007d8b9 (fixed)
Vendor states this is fixed in bedd7dee72588c838f5b67197ea8b387e7beb918 (fixed)
Vendor states this is fixed in d3d0eabe6e39b024deb3e085e2d408d037e967c3 (fixed)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card