Linux Kernel up to 7.1.7 igc igc_down resource consumption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00-

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.7. It has been rated as critical. This affects the function igc_down of the component igc. This manipulation causes resource consumption. This vulnerability appears as CVE-2026-80715. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 7.1.7. Affected by this vulnerability is the function igc_down of the component igc. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-80715 since 08/26/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

Upgrading to version 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.44 or 7.1.8 eliminates this vulnerability. Applying the patch ad6e0df267dc96edb7de1fa0a2fb2a70645bff86/605585a8d89aaeb0122e9016fdaa92376897a705/a0f16c337691813f8d8f014c01fff5a368e08898/f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2/3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668/9a2b637aef4e515c2179774888441d00e8a5ae95/5ffab5b9589c50e4cfc0cf36ffd76c89422d4019 is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Resource consumption
CWE: CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.217/6.1.184/6.6.153/6.12.105/6.18.44/7.1.8
Patch: ad6e0df267dc96edb7de1fa0a2fb2a70645bff86/605585a8d89aaeb0122e9016fdaa92376897a705/a0f16c337691813f8d8f014c01fff5a368e08898/f929a6fe5b7ae1e72d2c6d18cd69ab90dcf689d2/3b5aee6fcbf6b58112d40d19c8d31fa3f78ee668/9a2b637aef4e515c2179774888441d00e8a5ae95/5ffab5b9589c50e4cfc0cf36ffd76c89422d4019

Timelineinfo

08/26/2026 CVE reserved
08/28/2026 +2 days Advisory disclosed
08/28/2026 +0 days VulDB entry created
08/28/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80715 (🔒)
GCVE (CVE): GCVE-0-2026-80715
GCVE (VulDB): GCVE-100-396613

Entryinfo

Created: 08/28/2026 10:49
Changes: 08/28/2026 10:49 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!