Impact
A concurrency bug in the Linux cXGB4 driver allows a receive softirq to interrupt a flush operation on the shared XArray without disabling softirqs, causing the receiving task to spin on a lock held by the interrupted task. This race condition can make the kernel’s networking stack unresponsive, effectively denying network service for the affected CPU. The bug manifests when tid_list entries are erased while softirqs remain enabled, a scenario that is logically incorrect according to the kernel’s locking requirements.
Affected Systems
Linux kernel implementations featuring the cXGB4 network driver. No specific kernel release numbers are listed in the available data, so all current kernels with this driver present are potentially affected.
Risk and Exploitability
The EPSS score is less than 1%, and the CVSS is 5.9, indicating moderate risk. It is not listed in the KEV catalog. The likely attack vector requires generating network traffic that triggers a receive softirq on a CPU where the driver is actively erasing entries. No public exploitation examples exist, but the impact is a denial of service that could be triggered by either local or remote actors who can induce the packet path.
OpenCVE Enrichment