CVE-2026-90417: Linux kernel · RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry()
Source GCVE Database
Not known to be exploited · fixed in 379cf06e6fe34af980064c6ccaf15d8e26ec4a42 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 18:21 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 379cf06e6fe34af980064c6ccaf15d8e26ec4a42, 373f3716a2de7adc739269ebb4d87e5bf4dc180c, 68c1d2c085f205e8a5338bc3d3304f897deca4d9 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by correcting skb ownership and freeing logic in write_tpt_entry() and related functions. Users should apply the official kernel updates containing this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory or Linux kernel mailing lists for the official fixed versions and apply updates accordingly.
Description
A vulnerability in the Linux kernel's RDMA/cxgb4 driver involves a memory leak and a double free error in the write_tpt_entry() function. The issue occurs when the device is in a fatal error state or when allocation failures happen, leading to improper handling of skb buffers. This results in a memory leak of dereg_skb and a double free of skb, which could cause kernel instability or crashes. The flaw has been fixed by making write_tpt_entry() the sole owner of the skb and ensuring proper freeing behavior before handing off to the transmit path.
References
- nvd.nist.gov/vuln/detail/CVE-2026-90417 (opens in a new tab)
- git.kernel.org/stable/c/26c6e9bc0b907b880c5d8486291f0452c8227fbe (opens in a new tab)
- git.kernel.org/stable/c/2fcd26f4680143e9ec477069530548dbe20fce6f (opens in a new tab)
- git.kernel.org/stable/c/373f3716a2de7adc739269ebb4d87e5bf4dc180c (opens in a new tab)
- git.kernel.org/stable/c/379cf06e6fe34af980064c6ccaf15d8e26ec4a42 (opens in a new tab)
- git.kernel.org/stable/c/68c1d2c085f205e8a5338bc3d3304f897deca4d9 (opens in a new tab)
- git.kernel.org/stable/c/6b15fc9bc117fb6597fa1c2cc30284aafe71101c (opens in a new tab)