igc: remove napi_synchronize() in igc_down()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fc9df2a0b520d7d439ecf464794d53e91be74b93 · < 9a2b637aef4e515c2179774888441d00e8a5ae95| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
igc: remove napi_synchronize() in igc_down()
When an AF_XDP zero-copy application is killed abruptly, the XSK pool is torn down but NAPI keeps polling. igc_clean_rx_irq_zc() then returns the full budget on every poll, so napi_complete_done() never clears NAPI_STATE_SCHED.
igc_down() calls napi_synchronize() before napi_disable(), so it spins forever waiting for that bit and the interface never goes down. Drop the napi_synchronize() and let napi_disable() do the job -- it sets NAPI_STATE_DISABLE, which forces the stuck poll to complete. Reorder it ahead of igc_set_queue_napi() so the NAPI mapping is cleared only after polling has stopped, matching the recent igb fix b1e067240379.
From the CVE record · Linux
The Linux kernel’s igc driver can get stuck when an AF_XDP zero-copy application is killed abruptly. Its XSK pool is torn down while NAPI keeps polling, causing interface shutdown to hang. This requires a local application using AF_XDP zero-copy; the input does not specify authentication requirements.
Engineers running Linux systems that use the igc driver with AF_XDP zero-copy applications should check their kernel; affected versions are not specified.