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-92514RDMA/erdma: Fix CEQ tasklet use-after-free on removal

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/erdma: Fix CEQ tasklet use-after-free on removal Each CEQ interrupt handler only schedules eqc->tasklet. The tasklet calls erdma_ceq_completion_handler(), which reads the DMA-coherent EQ ring through get_next_valid_eqe() and updates eq->dbrec through notify_eq(). erdma_ceqs_uninit() frees each CEQ IRQ and then destroys its EQ. free_irq() prevents another hard IRQ and waits for an in-flight handler, but it does not drain a tasklet that the handler already scheduled. The tasklet can therefore access eq->qbuf or eq->dbrec after erdma_eq_destroy() frees them. Clearing ceq_cb->ready does not synchronize with a tasklet that already passed the check at the start of erdma_ceq_completion_handler(). Kill the tasklet after free_irq(), when no handler can schedule it again, and before erdma_ceq_uninit_one() releases the EQ buffers.

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.21% · top 89% of all CVEs (16 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 f2a0a630b953451a59a2612ad8c29246638f0a38 – < 0e8b78dabb1f156db05ffe74c6eae861167c7c21
    • affected f2a0a630b953451a59a2612ad8c29246638f0a38 – < 6e129c1310abfa786a510cc63e69c5ef12349048
    • affected f2a0a630b953451a59a2612ad8c29246638f0a38 – < f738c0a372d36a10dfae6dc357717c13b2aa72f4
    • affected f2a0a630b953451a59a2612ad8c29246638f0a38 – < a60c36d8d17f1b86705523d5eb6d290df28831e5
    • affected f2a0a630b953451a59a2612ad8c29246638f0a38 – < 61a25b8d333e1eb2a189881d516f8d5194e26840
    • affected f2a0a630b953451a59a2612ad8c29246638f0a38 – < 0ca79979384f031d710c4b3bae065dcb5d95aca3
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • 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-92514 badge
[![CVE-2026-92514](https://cveledger.app/badge/CVE-2026-92514.svg)](https://cveledger.app/cve/CVE-2026-92514)

Record last updated .