igc: remove napi_synchronize() in igc_down()

Answer in brief

CVE-2026-80715 records a Unknown severity vulnerability in igc: remove napi_synchronize() in igc_down(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Aug 28, 2026Source checked Aug 28, 2026First seen by HOL Aug 28, 2026Material review Aug 28, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=fc9df2a0b520d7d439ecf464794d53e91be74b93 <ad6e0df267dc96edb7de1fa0a2fb2a70645bff86 \|\| >=fc9df2a0b520d7d439ecf464794d53e91be74b93 <605585a8d89aaeb0122e9016fdaa92376897a705 \|\| >=fc9df2a0b520d7d439ecf464794d53e91be74b93 <a0f16c337691813f8d8f014c01fff5a368e08898 \|\| >=fc9df2a0b520d7d439ecf464794d53e91be74b93 <f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2 \|\| >=fc9df2a0b520d7d439ecf464794d53e91be74b93 <3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668 \|\| >=fc9df2a0b520d7d439ecf464794d53e91be74b93 <9a2b637aef4e515c2179774888441d00e8a5ae95 \|\| >=fc9df2a0b520d7d439ecf464794d53e91be74b93 <5ffab5b9589c50e4cfc0cf36ffd76c89422d4019	ad6e0df267dc96edb7de1fa0a2fb2a70645bff86, 605585a8d89aaeb0122e9016fdaa92376897a705, a0f16c337691813f8d8f014c01fff5a368e08898, f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2, 3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668, 9a2b637aef4e515c2179774888441d00e8a5ae95, 5ffab5b9589c50e4cfc0cf36ffd76c89422d4019
Linux/Linuxgeneric	5.14	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to ad6e0df267dc96edb7de1fa0a2fb2a70645bff86 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 28, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.