Skip to main content
VulnerabilityPublished Updated

CVE-2026-64035: Linux kernel · igc: set tx buffer type for SMD frames

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 5acc641e590e008caaed480ed9ffae47cf7ecbdf : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in 5acc641e590e008caaed480ed9ffae47cf7ecbdf, 1f83545f432d106d5fc71d3997b2d382104ebcc4, 1c8587bd025244aa52061f5ceecbf5e68a1063d9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Linux kernel to 5acc641e590e008caaed480ed9ffae47cf7ecbdf, 1f83545f432d106d5fc71d3997b2d382104ebcc4 or 1c8587bd025244aa52061f5ceecbf5e68a1063d9.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 5422570c0010bb968738f9256eb2bf83e79b4d63, < 5acc641e590e008caaed480ed9ffae47cf7ecbdf
Fixed in
  • 5acc641e590e008caaed480ed9ffae47cf7ecbdf
LinuxLinuxAffected
  • ≥ 5422570c0010bb968738f9256eb2bf83e79b4d63, < 1f83545f432d106d5fc71d3997b2d382104ebcc4
Fixed in
  • 1f83545f432d106d5fc71d3997b2d382104ebcc4
LinuxLinuxAffected
  • ≥ 5422570c0010bb968738f9256eb2bf83e79b4d63, < 1c8587bd025244aa52061f5ceecbf5e68a1063d9
Fixed in
  • 1c8587bd025244aa52061f5ceecbf5e68a1063d9
LinuxLinuxAffected
  • =6.16
Fixed in–

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.

References

Community reviews

Loading reviews…