cve.bz

CVE-2026-64035 linux linux kernel: Missing Initialization of Resource

9.8 criticalEPSS 0.4%Fix available

Critical (9.8) in linux linux kernel. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-909 Missing Initialization of Resource
CWE-665 Improper Initialization
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-64035 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64035?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64035?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64035 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.34
Linux7.07.0.11
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.0.12-1DEBIAN-CVE-2026-64035
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-64035
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-64035
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-64035
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-64035
Ubuntu24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-64035 USN-8728-2
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-64035
Ubuntu24.04:LTSlinux-gcp-7.0, linux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-64035 USN-8728-1 USN-8728-3
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-64035
Ubuntu24.04:LTSlinux-nvidia-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-64035 USN-8663-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 24 moreno fix listedUBUNTU-CVE-2026-64035
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-28.28.1~24.04.3UBUNTU-CVE-2026-64035
Ubuntu26.04:LTSlinux7.0.0-28.28UBUNTU-CVE-2026-64035
9 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 29 more0:5.14.0-687.56.1.el9_8RHSA-2026:77689
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 31 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-687.56.1.el9_8RHSA-2026:77689
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 47 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-687.56.1.el9_8RHSA-2026:77689
Red Hatenterprise_linux:9::crblibperf, rv-debuginfo, perf-debuginfo and 18 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-687.56.1.el9_8RHSA-2026:77689
Red Hatenterprise_linux:9::nfvkernel-rt, rv-debuginfo, kernel-rt-core and 25 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-687.56.1.el9_8RHSA-2026:77689
Red Hatenterprise_linux:9::realtimekernel-rt, rv-debuginfo, kernel-rt-64k and 37 more0:5.14.0-741.20.1.el9_9RHSA-2026:97873
Red Hatenterprise_linux:10.2rv, perf, rtla and 88 more0:6.12.0-211.64.1.el10_2RHSA-2026:77690
Red Hatshadow_migration_toolkit:10::el10kernel-modules-internal0:6.12.0-211.64.1.el10_2RHSA-2026:77690
AlmaLinux9rv, perf, rtla and 71 more5.14.0-687.56.1.el9_8ALSA-2026:77689
AlmaLinux10rv, perf, rtla and 72 more6.12.0-211.64.1.el10_2ALSA-2026:77690
Rocky Linux9kernel0:5.14.0-687.56.1.el9_8RLSA-2026:77689
Rocky Linux9rv, perf, rtla and 88 more0:5.14.0-741.20.1.el9_9RLSA-2026:97873
Rocky Linux10kernel0:6.12.0-211.64.1.el10_2RLSA-2026:77690
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-64035

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A stale tx buffer type in the igc driver can make SMD frame TX completion use a cleanup path that does not match the object actually stored in the reused descriptor. The affected entry is initialized as an skb but may still carry an older XDP or XSK type, so completion can treat the buffer as the wrong object type and may free or release it incorrectly. For the CVSS the PR:L is used in the paranoid score because reliable triggering may be possible for a local user or service with delegated network administration, XDP, XSK, or reduced capability access rather than only full host root. The issue is not directly network reachable and depends on Intel igc hardware plus frame preemption verification and TX buffer reuse conditions. Impact is at least local denial of service via driver or kernel crash, and in worst case may allow confidentiality or integrity impact due to wrong cleanup path memory corruption.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-211.64.1.el10_2Fixed 2026-10-08RHSA-2026:77690
Red Hat Enterprise Linux 9kernel-0:5.14.0-687.56.1.el9_8Fixed 2026-10-08RHSA-2026:77689
Shadow Migration Toolkit for Virtualization for RHEL 10kernel-0:6.12.0-211.64.1.el10_2Fixed 2026-10-08RHSA-2026:77690
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-64035.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON