Menu

Star on GitHub · 3.2k

CVE-2026-31691

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: igb: remove napi_synchronize() in igb_down() When an AF_XDP zero-copy application terminates abruptly (e.g., kill -9), the XSK…

Published Apr 27, 2026EPSS 0.16%

Overview

CVE-2026-31691 is a medium-severity vulnerability. It was published on April 27, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

igb: remove napi_synchronize() in igb_down()

When an AF_XDP zero-copy application terminates abruptly (e.g., kill -9),

the XSK buffer pool is destroyed but NAPI polling continues.

igb_clean_rx_irq_zc() repeatedly returns the full budget, preventing

napi_complete_done() from clearing NAPI_STATE_SCHED.

igb_down() calls napi_synchronize() before napi_disable() for each queue

vector. napi_synchronize() spins waiting for NAPI_STATE_SCHED to clear,

which never happens. igb_down() blocks indefinitely, the TX watchdog

fires, and the TX queue remains permanently stalled.

napi_disable() already handles this correctly: it sets NAPI_STATE_DISABLE.

After a full-budget poll, __napi_poll() checks napi_disable_pending(). If

set, it forces completion and clears NAPI_STATE_SCHED, breaking the loop

that napi_synchronize() cannot.

napi_synchronize() was added in commit 41f149a285da ("igb: Fix possible

panic caused by Rx traffic arriv

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-31691?

CVE-2026-31691 is a medium-severity vulnerability. It was published on April 27, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2026-31691?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31691?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31691?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31691 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all