Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 99fa331dc8629be55ac7a0cca0dc56492070ddac – < 5eb0c57a8b568eb08f464861d84d518a2af939ac
    • affected 99fa331dc8629be55ac7a0cca0dc56492070ddac – < d5cc211e8c39e46f357d30a092d683e84d560de9
    • affected 99fa331dc8629be55ac7a0cca0dc56492070ddac – < 2f0c6705e26ba92c0c6b0b0908a2d3f35a039d5b
    • affected 99fa331dc8629be55ac7a0cca0dc56492070ddac – < 8c013e3a8d8273da4d47bf1c27f016a3551996f5
    • affected 99fa331dc8629be55ac7a0cca0dc56492070ddac – < 64c72390d8407ea86de712a477c796b07d37abc4
    • affected 99fa331dc8629be55ac7a0cca0dc56492070ddac – < 235ef2d0e750885c29340b0fc40620a7a4f52e12
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-92509 badge
[![CVE-2026-92509](https://cveledger.app/badge/CVE-2026-92509.svg)](https://cveledger.app/cve/CVE-2026-92509)

Record last updated .