CVE-2026-23122: igc: Reduce TSN TX packet buffer from 7KB to 5KB per queue
In the Linux kernel, the following vulnerability has been resolved:
igc: Reduce TSN TX packet buffer from 7KB to 5KB per queue
The previous 7 KB per queue caused TX unit hangs under heavy
timestamping load. Reducing to 5 KB avoids these hangs and matches
the TSN recommendation in I225/I226 SW User Manual Section 7.5.4.
The 8 KB "freed" by this change is currently unused. This reduction
is not expected to impact throughput, as the i226 is PCIe-limited
for small TSN packets rather than TX-buffer-limited.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel network driver reliability flaw. Under heavy timestamping load, affected igc driver configurations can hang the transmit unit. The business impact is likely service degradation or network disruption on specific Intel I225/I226 Ethernet deployments using TSN features, not confirmed data theft or remote code execution.
Executive priority
Treat as targeted operational reliability risk. Patch during normal kernel maintenance, but accelerate for plants, appliances, or network-dependent services using Intel I225/I226 TSN workloads.
Technical view
The kernel fix reduces igc TSN transmit packet buffer allocation from 7 KB to 5 KB per queue, aligning with I225/I226 guidance. The stated failure mode is TX unit hangs under heavy timestamping load. The provided record lists affected Linux kernel versions and two stable commits, but no CVSS, CWE, or exploitation evidence.
Likely exposure
Exposure appears limited to affected Linux kernel versions using the igc driver with I225/I226 Ethernet hardware, especially TSN or timestamping-heavy workloads. General Linux systems without this driver or workload are less likely exposed based on the provided sources.
Exploitation context
The source bundle does not show active exploitation. KEV is false, and the references describe a stability fix for heavy timestamping load rather than a public exploit scenario.
Researcher notes
The record lacks CVSS, CWE, and detailed attacker prerequisites. Analysis should remain conservative: availability impact is supported, but exploitability, remote reachability, and security boundary implications are not established by the provided sources.
Mitigation direction
Upgrade to a Linux kernel containing the referenced stable igc fixes.
Use vendor or distribution kernel advisories to confirm fixed package versions.
Prioritize systems using igc with I225/I226 adapters and TSN workloads.
If patches are unavailable, reduce timestamping-heavy TSN load where operationally feasible.
Monitor vendor guidance for any updated severity or workaround information.
Validation and detection
Inventory Linux kernel versions against the affected range in the CVE record.
Identify systems loading the igc driver with I225/I226 Ethernet hardware.
Confirm whether kernel builds include the referenced stable commit fixes.
Review logs and monitoring for TX unit hangs under timestamping-heavy traffic.
Validate remediation first in representative TSN or timestamping workloads.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23122 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 15:09 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.