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-98430RDMA/efa: Keep admin queues alive while IRQ is registered

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/efa: Keep admin queues alive while IRQ is registered The management IRQ handler accesses both the admin completion queue and the async event queue. The driver registered the IRQ before constructing these queues and destroyed them before freeing the IRQ, so the handler's lifetime was not contained by the resources it accesses. Initialize the queues with interrupts masked, request the IRQ, and then switch to interrupt mode. On removal, reset the device and free the IRQ before destroying the queues. Also reset the device before destroying the queues if IRQ registration fails, because the device already has their DMA addresses.

Timeline

  1. ID reserved

    By Linux

  2. · 19 days later

    Published

  3. · 5 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 88% 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 b7f5e880f3774ff1934ce272e1c3b673a3a9c414 – < 0a8a105978e5ace0d885964317c5aed8ab4c0a0c
    • affected b7f5e880f3774ff1934ce272e1c3b673a3a9c414 – < 00f7df59543cce445cfd2f109ace88c17d8aef4d
    • affected b7f5e880f3774ff1934ce272e1c3b673a3a9c414 – < bc7e64bad96c23fb343f47689670d0037f1a65e7
    • affected b7f5e880f3774ff1934ce272e1c3b673a3a9c414 – < d2a1c0bf4139c17b8d7668322b78c28d8c5b2dd0
    • affected b7f5e880f3774ff1934ce272e1c3b673a3a9c414 – < cf5520d1c931a70ccce0a1a247113bcec47a42be
    • affected b7f5e880f3774ff1934ce272e1c3b673a3a9c414 – < e08aca85c02ff290f785f07acae758f0daf5f49e
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 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-98430 badge
[![CVE-2026-98430](https://cveledger.app/badge/CVE-2026-98430.svg)](https://cveledger.app/cve/CVE-2026-98430)

Record last updated .