GHSA-CCPX-W89W-V2MX
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In 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().
{
"affected": [],
"aliases": [
"CVE-2026-90417"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:46Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry()\n\nWhen the device is in the fatal error state, write_tpt_entry() returns -EIO\nbefore handing the caller\u0027s preallocated skb to the transmit path; its\nallocation-failure returns do the same. c4iw_dereg_mr() ignores the error\nand frees mhp, leaking mhp-\u003edereg_skb. c4iw_get_dma_mr() instead frees the\nskb a second time after dereg_mem() already consumed it, a double free.\n\nMake write_tpt_entry() the sole owner of a non-NULL skb, freeing it on\nevery return preceding handoff to c4iw_ofld_send(): fatal error, tpt and\nstag allocation failure. c4iw_ofld_send() consumes the skb on success and\nerror alike, so drop the redundant kfree_skb() in c4iw_get_dma_mr() after\ndereg_mem().",
"id": "GHSA-ccpx-w89w-v2mx",
"modified": "2026-09-17T18:32:04Z",
"published": "2026-09-17T18:32:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90417"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/373f3716a2de7adc739269ebb4d87e5bf4dc180c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6b15fc9bc117fb6597fa1c2cc30284aafe71101c"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.