What is CVE-2026-64110?

CVE-2026-64110 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Memory Leak flaw (CWE-401), affecting Linux kernel versions from 6.16 onward and patched in 6.18.34, 7.0.11 and 7.1. CVE-2026-64110 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-64110?

CVE-2026-64110 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2026-64110?

Yes, CVE-2026-64110 has been patched. Fixed versions include 6.18.34, 7.0.11 and 7.1. If you are running Linux kernel 6.16 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-64110 actively exploited?

CVE-2026-64110 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Memory Leak (CWE-401)?

The product does not release memory after use, causing gradual resource exhaustion. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/401.html

CVE-2026-64110

Medium

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

Package Linux Kernel

Published 2026-07-19

Last modified 2026-08-12

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-401

CVE-2026-64110 is a Memory Leak vulnerability

What is Memory Leak?

The product does not release memory after use, causing gradual resource exhaustion. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.16 and later are affected. Fixed in 6.18.34, 7.0.11, 7.1 and their respective stable series.

Affected from

≥ 6.16

Fixed in

✓ 6.18.34 6.18.x ✓ 7.0.11 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/3ebf056556138e74c640e6dc2b3848abd398b460

Patch
Kernel Git
https://git.kernel.org/stable/c/e935c37b8a94bb256fada6395a5d05e1c0c6bdaf

Patch
Kernel Git
https://git.kernel.org/stable/c/f1bafd35f11b3aca1c7bb38da173b8787364a04c

Patch

Details

CVE ID CVE-2026-64110

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-07-19

Modified 2026-08-12

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64110?

CVE-2026-64110 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as a Memory Leak flaw (CWE-401) . It affects Linux kernel versions from 6.16 onward and has been patched in 6.18.34, 7.0.11 and 7.1. CVE-2026-64110 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64110?

CVE-2026-64110 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2026-64110?

Yes. CVE-2026-64110 has been patched. Fixed versions include 6.18.34, 7.0.11 and 7.1. If you are running Linux kernel 6.16 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-64110 actively exploited?

No. CVE-2026-64110 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.