VulnerabilityPublished 19 Jul 2026Updated 6 Nov 2026

CVE-2026-64110: Linux kernel · igc: fix potential skb leak in igc_fpe_xmit_smd_frame()

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in f1bafd35f11b3aca1c7bb38da173b8787364a04c : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in f1bafd35f11b3aca1c7bb38da173b8787364a04c, e935c37b8a94bb256fada6395a5d05e1c0c6bdaf, 3ebf056556138e74c640e6dc2b3848abd398b460

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 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 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to f1bafd35f11b3aca1c7bb38da173b8787364a04c, e935c37b8a94bb256fada6395a5d05e1c0c6bdaf or 3ebf056556138e74c640e6dc2b3848abd398b460.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 5422570c0010bb968738f9256eb2bf83e79b4d63, < f1bafd35f11b3aca1c7bb38da173b8787364a04c	Fixed in f1bafd35f11b3aca1c7bb38da173b8787364a04c
LinuxLinux	Affected ≥ 5422570c0010bb968738f9256eb2bf83e79b4d63, < e935c37b8a94bb256fada6395a5d05e1c0c6bdaf	Fixed in e935c37b8a94bb256fada6395a5d05e1c0c6bdaf
LinuxLinux	Affected ≥ 5422570c0010bb968738f9256eb2bf83e79b4d63, < 3ebf056556138e74c640e6dc2b3848abd398b460	Fixed in 3ebf056556138e74c640e6dc2b3848abd398b460
LinuxLinux	Affected =6.16	Fixed in–

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

References

Community reviews

Loading reviews…