In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igc_fpe_xmit_smd_frame() When… (CVE-2026-64110)
In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igc_fpe_xmit_smd_frame() When igc_fpe_init_tx_descriptor() fails, no one takes care of an allocated skb, leaking it. [1] Use dev_kfree_skb_any() on failure. Tested on an I226 adapter with the following command, while injecting faults in igc_fpe_init_tx_descriptor() to trigger the error path. # ethtool --set-mm $DEV verify-enabled on tx-enabled on pmac-enabled on [1] unreferenced object 0xffff888113c6cdc0 (size 224): ... backtrace (crc be3d3fda): kmem_cache_alloc_node_noprof+0x3b1/0x410 __alloc_skb+0xde/0x830 igc_fpe_xmit_smd_frame.isra.0+0xad/0x1b0 igc_fpe_send_mpacket+0x37/0x90 ethtool_mmsv_verify_timer+0x15e/0x300
AI Analysis
Technical Summary
The Linux kernel igc driver contained a flaw where, upon failure of igc_fpe_init_tx_descriptor(), the allocated socket buffer (skb) was not freed, causing a memory leak. This was identified and fixed by adding a call to dev_kfree_skb_any() in the error path within igc_fpe_xmit_smd_frame(). The fix was tested on an I226 adapter with fault injection to confirm the resolution.
Potential Impact
The vulnerability leads to a potential memory leak in the kernel network driver, which could degrade system stability or performance over time due to unreleased memory. There is no indication of direct code execution or privilege escalation impact from the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by properly freeing the allocated skb on failure. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igc_fpe_xmit_smd_frame() When… (CVE-2026-64110)
Description
In the Linux kernel, the following vulnerability has been resolved: igc: fix potential skb leak in igc_fpe_xmit_smd_frame() When igc_fpe_init_tx_descriptor() fails, no one takes care of an allocated skb, leaking it. [1] Use dev_kfree_skb_any() on failure. Tested on an I226 adapter with the following command, while injecting faults in igc_fpe_init_tx_descriptor() to trigger the error path. # ethtool --set-mm $DEV verify-enabled on tx-enabled on pmac-enabled on [1] unreferenced object 0xffff888113c6cdc0 (size 224): ... backtrace (crc be3d3fda): kmem_cache_alloc_node_noprof+0x3b1/0x410 __alloc_skb+0xde/0x830 igc_fpe_xmit_smd_frame.isra.0+0xad/0x1b0 igc_fpe_send_mpacket+0x37/0x90 ethtool_mmsv_verify_timer+0x15e/0x300
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel igc driver contained a flaw where, upon failure of igc_fpe_init_tx_descriptor(), the allocated socket buffer (skb) was not freed, causing a memory leak. This was identified and fixed by adding a call to dev_kfree_skb_any() in the error path within igc_fpe_xmit_smd_frame(). The fix was tested on an I226 adapter with fault injection to confirm the resolution.
Potential Impact
The vulnerability leads to a potential memory leak in the kernel network driver, which could degrade system stability or performance over time due to unreleased memory. There is no indication of direct code execution or privilege escalation impact from the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by properly freeing the allocated skb on failure. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the exact fixed versions and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-hhg7-m4q3-pm9j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64110"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912b57c
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:48:02 UTC
Last updated: 09/03/2026, 22:52:13 UTC
Views: 106
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.