CVE-2026-23122
TX Buffer Overflow Risk in Linux igc Driver Causing Hangs
Publication date: 2026-02-14
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.16 (inc) to 6.18.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability relates to the Linux kernel's handling of the igc network driver, specifically concerning the TSN (Time-Sensitive Networking) TX packet buffer size per queue.
Previously, the TX packet buffer was set to 7 KB per queue, which caused the TX unit to hang under heavy timestamping load. The vulnerability was that this buffer size could lead to hangs during heavy TSN traffic.
The fix involved reducing the TX packet buffer size from 7 KB to 5 KB per queue, which prevents these hangs and aligns with the TSN recommendation in the I225/I226 software user manual.
How can this vulnerability impact me? :
The impact of this vulnerability is that under heavy timestamping load, the TX unit in the network driver could hang, potentially causing network transmission issues or interruptions.
By causing hangs, this could lead to degraded network performance or temporary loss of network connectivity in systems using the affected driver and hardware.
However, the fix reduces the buffer size to prevent these hangs without impacting throughput, so normal network performance should be maintained after the fix.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know