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-90417RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry()

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry() When the device is in the fatal error state, write_tpt_entry() returns -EIO before handing the caller's preallocated skb to the transmit path; its allocation-failure returns do the same. c4iw_dereg_mr() ignores the error and frees mhp, leaking mhp->dereg_skb. c4iw_get_dma_mr() instead frees the skb a second time after dereg_mem() already consumed it, a double free. Make write_tpt_entry() the sole owner of a non-NULL skb, freeing it on every return preceding handoff to c4iw_ofld_send(): fatal error, tpt and stag allocation failure. c4iw_ofld_send() consumes the skb on success and error alike, so drop the redundant kfree_skb() in c4iw_get_dma_mr() after dereg_mem().

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 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.22% · top 87% 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 0f8ab0b6e91b4d5302ceee5ec12ce54d81297635 – < 26c6e9bc0b907b880c5d8486291f0452c8227fbe
    • affected 0f8ab0b6e91b4d5302ceee5ec12ce54d81297635 – < 68c1d2c085f205e8a5338bc3d3304f897deca4d9
    • affected 0f8ab0b6e91b4d5302ceee5ec12ce54d81297635 – < 379cf06e6fe34af980064c6ccaf15d8e26ec4a42
    • affected 0f8ab0b6e91b4d5302ceee5ec12ce54d81297635 – < 2fcd26f4680143e9ec477069530548dbe20fce6f
    • affected 0f8ab0b6e91b4d5302ceee5ec12ce54d81297635 – < 6b15fc9bc117fb6597fa1c2cc30284aafe71101c
    • affected 0f8ab0b6e91b4d5302ceee5ec12ce54d81297635 – < 373f3716a2de7adc739269ebb4d87e5bf4dc180c
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 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-90417 badge
[![CVE-2026-90417](https://cveledger.app/badge/CVE-2026-90417.svg)](https://cveledger.app/cve/CVE-2026-90417)

Record last updated .