# CVE-2026-80715: igc: remove napi_synchronize() in igc_down()

> A local attacker can cause a denial of service by abruptly killing an AF_XDP application, leading to a kernel hang in the igc network driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** AZL-98112, BELL-CVE-2026-80715, DEBIAN-CVE-2026-80715, GHSA-7phj-65qv-78j8, UBUNTU-CVE-2026-80715

## What is CVE-2026-80715?

CVE-2026-80715 is a denial of service vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80715?


## How do I fix CVE-2026-80715?

Apply the vendor's patch.

## Is CVE-2026-80715 being exploited?

There is no known exploitation of CVE-2026-80715 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80715 and fix it if it is affected.

What it is: CVE-2026-80715 is a denial of service vulnerability in Linux, published on 28 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80715 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80715/ (Markdown: https://insights.sbomify.com/CVE-2026-80715/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80715
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80715
- OSV: https://osv.dev/vulnerability/CVE-2026-80715

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80715/
Summaries are generated and may contain mistakes; the official description above is the record.