igc: remove napi_synchronize() in igc_down()
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.
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- EPSS
- 0.2% · 5th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.14affected
- fc9df2a0b520d7d439ecf464794d53e91be74b93 and later · before ad6e0df267dc96edb7de1fa0a2fb2a70645bff86affected · git
- fc9df2a0b520d7d439ecf464794d53e91be74b93 and later · before 605585a8d89aaeb0122e9016fdaa92376897a705affected · git
- fc9df2a0b520d7d439ecf464794d53e91be74b93 and later · before a0f16c337691813f8d8f014c01fff5a368e08898affected · git
- fc9df2a0b520d7d439ecf464794d53e91be74b93 and later · before f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2affected · git
- fc9df2a0b520d7d439ecf464794d53e91be74b93 and later · before 3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668affected · git
- fc9df2a0b520d7d439ecf464794d53e91be74b93 and later · before 9a2b637aef4e515c2179774888441d00e8a5ae95affected · git
- fc9df2a0b520d7d439ecf464794d53e91be74b93 and later · before 5ffab5b9589c50e4cfc0cf36ffd76c89422d4019affected · git
- before 5.14not affected · semver
- 5.15.217 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668 | Vendor (CNA) |
| Linux Linux | 5ffab5b9589c50e4cfc0cf36ffd76c89422d4019 | Vendor (CNA) |
| Linux Linux | 605585a8d89aaeb0122e9016fdaa92376897a705 | Vendor (CNA) |
| Linux Linux | 9a2b637aef4e515c2179774888441d00e8a5ae95 | Vendor (CNA) |
| Linux Linux | a0f16c337691813f8d8f014c01fff5a368e08898 | Vendor (CNA) |
| Linux Linux | ad6e0df267dc96edb7de1fa0a2fb2a70645bff86 | Vendor (CNA) |
| Linux Linux | f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668
- git.kernel.org/stable/c/5ffab5b9589c50e4cfc0cf36ffd76c89422d4019
- git.kernel.org/stable/c/605585a8d89aaeb0122e9016fdaa92376897a705
- git.kernel.org/stable/c/9a2b637aef4e515c2179774888441d00e8a5ae95
- git.kernel.org/stable/c/a0f16c337691813f8d8f014c01fff5a368e08898
- git.kernel.org/stable/c/ad6e0df267dc96edb7de1fa0a2fb2a70645bff86
- git.kernel.org/stable/c/f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.