CVE-2026-64035
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn the Linux kernel's igc (Intel Ethernet) driver, the function igc_fpe_init_smd_frame() initializes igc_tx_buffer fields for SMD (Single Mesh Datagram) socket buffers but fails to set the buffer type field. Since igc_tx_buffer entries are reused across transmissions, stale XDP or XSK buffer type values can persist, causing TX completion to execute the wrong memory cleanup path. This can lead to memory corruption, use-after-free, or system instability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify igc driver usageRun 'lsmod | grep igc' or check 'lspci -k | grep -A3 -i ethernet' to see if an Intel IGC network device is present and the driver is loadedAffected if The igc kernel module is loaded and managing a network interface
-
Check kernel versionRun 'uname -r' to get the running kernel versionAffected if The kernel version is older than the version containing the fix for this vulnerability in igc_fpe_init_smd_frame()
-
Verify driver source for the fixIf kernel source is available, examine drivers/net/ethernet/intel/igc/igc_main.c and search for 'igc_fpe_init_smd_frame' function; check if it contains assignment of 'buf->type = IGC_TX_BUFFER_TYPE_SKB' or equivalent buffer type settingAffected if The function igc_fpe_init_smd_frame() exists but does not set the buffer type field before returning
-
Check for SMD/FoE features in useExamine ethtool output for the interface (e.g., 'ethtool -k <interface>') for FPE (Frame Preemption) or SMD-related features that may be enabledAffected if Frame Preemption or SMD features are enabled on an igc-managed interface
The system is affected if it runs a vulnerable kernel version with the igc driver loaded and uses an Intel IGC network interface, particularly if FPE/SMD features are enabled, since the igc_fpe_init_smd_frame() function fails to set the buffer type field, allowing stale XDP/XSK buffer types to persist and cause incorrect TX completion cleanup.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the upstream Linux kernel patch that sets the buffer type to IGC_TX_BUFFER_TYPE_SKB in igc_fpe_init_smd_frame(). This typically involves updating the kernel to a version containing the fix or backporting the single-line change to the igc driver.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-64035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-64035 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data