Skip to main content
VulnerabilityPublished Updated

CVE-2026-92509: Linux kernel · RDMA/core: Fix potential use after free in counter_release()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in d5cc211e8c39e46f357d30a092d683e84d560de9 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d5cc211e8c39e46f357d30a092d683e84d560de9, 235ef2d0e750885c29340b0fc40620a7a4f52e12, 64c72390d8407ea86de712a477c796b07d37abc4 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 99fa331dc8629be55ac7a0cca0dc56492070ddac, < d5cc211e8c39e46f357d30a092d683e84d560de9
Fixed in
  • d5cc211e8c39e46f357d30a092d683e84d560de9
LinuxLinuxAffected
  • ≥ 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 235ef2d0e750885c29340b0fc40620a7a4f52e12
Fixed in
  • 235ef2d0e750885c29340b0fc40620a7a4f52e12
LinuxLinuxAffected
  • ≥ 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 64c72390d8407ea86de712a477c796b07d37abc4
Fixed in
  • 64c72390d8407ea86de712a477c796b07d37abc4
LinuxLinuxAffected
  • ≥ 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 8c013e3a8d8273da4d47bf1c27f016a3551996f5
Fixed in
  • 8c013e3a8d8273da4d47bf1c27f016a3551996f5
LinuxLinuxAffected
  • ≥ 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 5eb0c57a8b568eb08f464861d84d518a2af939ac
Fixed in
  • 5eb0c57a8b568eb08f464861d84d518a2af939ac
LinuxLinuxAffected
  • ≥ 99fa331dc8629be55ac7a0cca0dc56492070ddac, < 2f0c6705e26ba92c0c6b0b0908a2d3f35a039d5b
Fixed in
  • 2f0c6705e26ba92c0c6b0b0908a2d3f35a039d5b

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.

References

Community reviews

Loading reviews…