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-90219RDMA/cxgb4: Free debugfs on registration failure

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/cxgb4: Free debugfs on registration failure c4iw_alloc() creates the per-device debugfs tree (dev->debugfs_root via setup_debugfs()), but it is removed only in c4iw_remove(), not in c4iw_dealloc(). When RDMA device registration fails, the registration worker's err_dealloc_ctx path calls c4iw_dealloc() directly, bypassing c4iw_remove(), so the debugfs dentries leak and outlive the freed c4iw_dev. Move debugfs_remove_recursive() into c4iw_dealloc() so every path that frees ctx->dev also removes its debugfs tree.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days 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.23% · top 86% of all CVEs (14 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 49ea0c036ede81f126f1a9389d377999fdf5c5a1 – < 459b59f7ed56511d6529311cb4e5e482ebfcfb8e
    • affected 49ea0c036ede81f126f1a9389d377999fdf5c5a1 – < cd60992f09b7e83bfd3c76e3bb06b29f3e2fa0a8
    • affected 49ea0c036ede81f126f1a9389d377999fdf5c5a1 – < c332d9e7dce234d8bef78271d003a68ee943b61b
    • affected 49ea0c036ede81f126f1a9389d377999fdf5c5a1 – < f98e894ec029a752cf9c7f7834741bead0fb463d
    • affected 49ea0c036ede81f126f1a9389d377999fdf5c5a1 – < 479a7f90060e62bdd9bb4036ec0a70bf460f6d23
    • affected 49ea0c036ede81f126f1a9389d377999fdf5c5a1 – < 046425412529dbfca1433c8bef5641b271b4ab2a
    • affected 49ea0c036ede81f126f1a9389d377999fdf5c5a1 – < ea41b5630fa3d9877ce9ed8832cf5575f742bfbb
    • affected 49ea0c036ede81f126f1a9389d377999fdf5c5a1 – < fe5c16bb6252dea6025b748257ddc3b2665495b0
    • affected 98fa991017981b52dcc4dc3924fc8e1e83e41bf4
    • affected af92e4a595e006b498c44b617ea38f697eca3469
    • affected 9c0cec79e5c914662c2cf98b4a729c0fcc8c872e
    • affected 4.19.130 – < 4.20
    • affected 5.4.49 – < 5.5
    • affected 5.7.6 – < 5.8
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .