CVE-2025-71156

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> gve: defer interrupt enabling until NAPI registration<br /> <br /> Currently, interrupts are automatically enabled immediately upon<br /> request. This allows interrupt to fire before the associated NAPI<br /> context is fully initialized and cause failures like below:<br /> <br /> [ 0.946369] Call Trace:<br /> [ 0.946369] <br /> [ 0.946369] __napi_poll+0x2a/0x1e0<br /> [ 0.946369] net_rx_action+0x2f9/0x3f0<br /> [ 0.946369] handle_softirqs+0xd6/0x2c0<br /> [ 0.946369] ? handle_edge_irq+0xc1/0x1b0<br /> [ 0.946369] __irq_exit_rcu+0xc3/0xe0<br /> [ 0.946369] common_interrupt+0x81/0xa0<br /> [ 0.946369] <br /> [ 0.946369] <br /> [ 0.946369] asm_common_interrupt+0x22/0x40<br /> [ 0.946369] RIP: 0010:pv_native_safe_halt+0xb/0x10<br /> <br /> Use the `IRQF_NO_AUTOEN` flag when requesting interrupts to prevent auto<br /> enablement and explicitly enable the interrupt in NAPI initialization<br /> path (and disable it during NAPI teardown).<br /> <br /> This ensures that interrupt lifecycle is strictly coupled with<br /> readiness of NAPI context.