CVE-2025-71156: gve: defer interrupt enabling until NAPI registration
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] napipoll+0x2a/0x1e0 [ 0.946369] netrxaction+0x2f9/0x3f0 [ 0.946369] handlesoftirqs+0xd6/0x2c0 [ 0.946369] ? handleedgeirq+0xc1/0x1b0 [ 0.946369] irqexitrcu+0xc3/0xe0 [ 0.946369] commoninterrupt+0x81/0xa0 [ 0.946369] </IRQ> [ 0.946369] <TASK> [ 0.946369] asmcommoninterrupt+0x22/0x40 [ 0.946369] RIP: 0010:pvnativesafehalt+0xb/0x10
Use the IRQFNOAUTOEN 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-71156?
CVE-2025-71156 is classified as a medium severity vulnerability that can lead to potential denial of service.
How do I fix CVE-2025-71156?
To resolve CVE-2025-71156, update the Linux kernel to a patched version that defers interrupt enabling until NAPI registration.
What systems are affected by CVE-2025-71156?
CVE-2025-71156 affects the Linux kernel across various versions, impacting systems using this software.
What risks are associated with CVE-2025-71156?
The primary risk associated with CVE-2025-71156 is that it could allow interrupts to fire before the associated processing is ready, potentially leading to crashes.
Is there any workaround for CVE-2025-71156?
Currently, there are no documented workarounds for CVE-2025-71156; the recommended action is to apply the latest updates.