CVE-2026-64035

Description

A flaw was found in the Linux kernel's igc network driver. The igc_fpe_init_smd_frame() function, responsible for initializing transmit (TX) buffer fields for Stream-based Data (SMD) frames, does not correctly set the buffer type. This can result in stale XDP (eXpress Data Path) or XSK (AF_XDP socket) types persisting in reused TX buffer entries. Consequently, the system's TX completion process may follow an incorrect cleanup path, potentially leading to memory corruption or system instability.

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.

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.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.8N/A9.8
Attack VectorAdjacent NetworkN/ANetwork
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.