Linux Kernel igc Driver Transmit Queue Timeout Handling Vulnerability Causes Kernel Panic

Vulnerability

A vulnerability in the Linux kernel's igc network driver can lead to a kernel panic. This issue arises when the driver experiences a transmit queue timeout, which can occur during normal operation. The timeout triggers the ndo_tx_timeout callback, causing the driver to reset the network adapter. However, similar race conditions can occur when the network interface is being restarted, generating interrupts that interfere with the transmission process. These interruptions can cause the driver to improperly manage the transmit queues, leading to a use-after-free condition. When this happens, the kernel's reference counting mechanism underflows, allowing freed memory to be accessed, which can cause a crash or potentially be exploited.

Impact

This vulnerability can cause a kernel panic, abruptly terminating all processes and crashing the system. However, the underlying issue creates a use-after-free condition that could be exploited to execute arbitrary code under certain circumstances.

Reproduction

The vulnerability can be reproduced by causing a transmit queue timeout in the igc driver, which can be triggered during normal network operations. This timeout will invoke the ndo_tx_timeout callback, leading to a kernel panic. The issue can be exacerbated by manually bringing the network interface down and then back up, which can generate interrupts that disrupt the normal transmission process. This combination of events can create a race condition that the vulnerability exploits, causing a reference count underflow and a subsequent kernel crash.

Remediation

Users can upgrade to the latest version of the Linux kernel, where this vulnerability has been addressed. Instructions for downloading the updated kernel can be found on the official Linux kernel website.

Added: Dec 30, 2025, 4:31 PM
Updated: Dec 30, 2025, 4:31 PM

Vulnerability Rating

Custom Algorithm
spread
9.0
impact
2.5
exploitability
5.7
remediation
7.7
relevance
1.8
threat
4.8
urgency
2.9
incentive
1.7

Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.