Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected fc9df2a0b520d7d439ecf464794d53e91be74b93 – < ad6e0df267dc96edb7de1fa0a2fb2a70645bff86
    • affected fc9df2a0b520d7d439ecf464794d53e91be74b93 – < 605585a8d89aaeb0122e9016fdaa92376897a705
    • affected fc9df2a0b520d7d439ecf464794d53e91be74b93 – < a0f16c337691813f8d8f014c01fff5a368e08898
    • affected fc9df2a0b520d7d439ecf464794d53e91be74b93 – < f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2
    • affected fc9df2a0b520d7d439ecf464794d53e91be74b93 – < 3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668
    • affected fc9df2a0b520d7d439ecf464794d53e91be74b93 – < 9a2b637aef4e515c2179774888441d00e8a5ae95
    • affected fc9df2a0b520d7d439ecf464794d53e91be74b93 – < 5ffab5b9589c50e4cfc0cf36ffd76c89422d4019
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.153 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80715 badge
[![CVE-2026-80715](https://cveledger.app/badge/CVE-2026-80715.svg)](https://cveledger.app/cve/CVE-2026-80715)

Record last updated .