igc: remove napi_synchronize() in igc_down()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.14
References 7
git.kernel.org
- stable/c/ad6e0df267dc96edb7de1fa0a2fb2a70645bff86
- stable/c/605585a8d89aaeb0122e9016fdaa92376897a705
- stable/c/a0f16c337691813f8d8f014c01fff5a368e08898
- stable/c/f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2
- stable/c/3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668
- stable/c/9a2b637aef4e515c2179774888441d00e8a5ae95
- stable/c/5ffab5b9589c50e4cfc0cf36ffd76c89422d4019