CVE-2025-71156
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-23

Last updated on: 2026-02-26

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: gve: defer interrupt enabling until NAPI registration Currently, interrupts are automatically enabled immediately upon request. This allows interrupt to fire before the associated NAPI context is fully initialized and cause failures like below: [ 0.946369] Call Trace: [ 0.946369] <IRQ> [ 0.946369] __napi_poll+0x2a/0x1e0 [ 0.946369] net_rx_action+0x2f9/0x3f0 [ 0.946369] handle_softirqs+0xd6/0x2c0 [ 0.946369] ? handle_edge_irq+0xc1/0x1b0 [ 0.946369] __irq_exit_rcu+0xc3/0xe0 [ 0.946369] common_interrupt+0x81/0xa0 [ 0.946369] </IRQ> [ 0.946369] <TASK> [ 0.946369] asm_common_interrupt+0x22/0x40 [ 0.946369] RIP: 0010:pv_native_safe_halt+0xb/0x10 Use the `IRQF_NO_AUTOEN` flag when requesting interrupts to prevent auto enablement and explicitly enable the interrupt in NAPI initialization path (and disable it during NAPI teardown). This ensures that interrupt lifecycle is strictly coupled with readiness of NAPI context.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-23
Last Modified
2026-02-26
Generated
2026-06-16
AI Q&A
2026-01-23
EPSS Evaluated
2026-06-15
NVD
CVE-2025-71156
EUVD
EUVD-2026-4387
Affected Vendors & Products
Showing 5 associated CPEs
Vendor Product Version / Range
linux linux_kernel 6.19
linux linux_kernel 6.19
linux linux_kernel 6.19
linux linux_kernel From 6.13 (inc) to 6.18.4 (exc)
linux linux_kernel From 6.9 (inc) to 6.12.64 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves the premature enabling of interrupts before the associated NAPI (New API) context is fully initialized. Interrupts are currently enabled automatically upon request, which can cause interrupts to fire too early and lead to failures such as kernel call trace errors. The fix defers interrupt enabling until after NAPI registration by using the IRQF_NO_AUTOEN flag to prevent automatic enabling and explicitly enabling interrupts during NAPI initialization, ensuring the interrupt lifecycle is properly synchronized with the readiness of the NAPI context.

Impact Analysis

This vulnerability can cause system instability or failures due to interrupts firing before the NAPI context is ready, potentially leading to kernel errors or crashes. This can affect network performance and reliability on systems running the vulnerable Linux kernel, possibly resulting in degraded service or downtime.

Detection Guidance

This vulnerability can be detected by checking for kernel log messages indicating interrupt handling failures related to NAPI initialization. Specifically, look for call traces in the system logs similar to the example provided, which include __napi_poll, net_rx_action, handle_softirqs, and related interrupt functions. You can use commands like 'dmesg | grep -i irq' or 'journalctl -k | grep -i irq' to search for such interrupt-related errors in the kernel logs.

Mitigation Strategies

To mitigate this vulnerability, ensure that the Linux kernel is updated to a version where the fix is applied. The fix involves deferring interrupt enabling until NAPI registration by using the IRQF_NO_AUTOEN flag when requesting interrupts, preventing automatic enabling. Interrupts should then be explicitly enabled during NAPI initialization and disabled during NAPI teardown, ensuring the interrupt lifecycle is coupled with the readiness of the NAPI context.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-71156. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart