In the Linux kernel, the following vulnerability has been resolved: igc: set tx buffer type for SMD frames Sashiko pointed out that… (CVE-2026-64035)
In the Linux kernel, the following vulnerability has been resolved: igc: set tx buffer type for SMD frames Sashiko pointed out that igc_fpe_init_smd_frame() initializes igc_tx_buffer fields for an SMD skb, but does not set the buffer type: https://sashiko.dev/#/patchset/20260415025226.114115-1-kohei%40enjuk.jp Since igc_tx_buffer entries are reused, a stale XDP or XSK type can remain and make TX completion use the wrong cleanup path. Set the buffer type to IGC_TX_BUFFER_TYPE_SKB.
AI Analysis
Technical Summary
The Linux kernel igc driver had a vulnerability where the igc_fpe_init_smd_frame() function initialized igc_tx_buffer fields for SMD skb frames but did not set the buffer type field. Because igc_tx_buffer entries are reused, stale buffer types such as XDP or XSK could remain, causing the TX completion process to use an incorrect cleanup path. The fix involved setting the buffer type explicitly to IGC_TX_BUFFER_TYPE_SKB to prevent misuse of stale buffer types.
Potential Impact
The vulnerability could cause the transmit completion process to execute an incorrect cleanup routine due to stale buffer type information. This may lead to improper resource handling or memory corruption within the network driver context. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to set the tx buffer type correctly for SMD frames. Users should update to the kernel version that includes this patch. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation.
In the Linux kernel, the following vulnerability has been resolved: igc: set tx buffer type for SMD frames Sashiko pointed out that… (CVE-2026-64035)
Description
In the Linux kernel, the following vulnerability has been resolved: igc: set tx buffer type for SMD frames Sashiko pointed out that igc_fpe_init_smd_frame() initializes igc_tx_buffer fields for an SMD skb, but does not set the buffer type: https://sashiko.dev/#/patchset/20260415025226.114115-1-kohei%40enjuk.jp Since igc_tx_buffer entries are reused, a stale XDP or XSK type can remain and make TX completion use the wrong cleanup path. Set the buffer type to IGC_TX_BUFFER_TYPE_SKB.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel igc driver had a vulnerability where the igc_fpe_init_smd_frame() function initialized igc_tx_buffer fields for SMD skb frames but did not set the buffer type field. Because igc_tx_buffer entries are reused, stale buffer types such as XDP or XSK could remain, causing the TX completion process to use an incorrect cleanup path. The fix involved setting the buffer type explicitly to IGC_TX_BUFFER_TYPE_SKB to prevent misuse of stale buffer types.
Potential Impact
The vulnerability could cause the transmit completion process to execute an incorrect cleanup routine due to stale buffer type information. This may lead to improper resource handling or memory corruption within the network driver context. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to set the tx buffer type correctly for SMD frames. Users should update to the kernel version that includes this patch. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-85cw-fhvw-f94j
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64035"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912ced6
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:56:11 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 13
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.