LiveActive security incident?Get immediate response
CVE Record

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] __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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver availability issue in gve networking. An interrupt can arrive before the related NAPI network-processing context is ready, which can trigger kernel failures. The source bundle provides no CVSS score, CWE, or evidence of exploitation, so urgency depends on whether affected kernels and this driver are in use.

Executive priority

Handle as a targeted Linux kernel maintenance issue, not an emergency without exposure evidence. Prioritize patching for production hosts that use gve networking or where a kernel crash would create material outage risk.

Technical view

The gve driver requested interrupts in a way that enabled them immediately. That allowed IRQ handling to enter NAPI polling before NAPI registration completed. The fix requests IRQs with IRQF_NO_AUTOEN, then explicitly enables interrupts during NAPI initialization and disables them during teardown, aligning interrupt lifecycle with NAPI readiness.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions with the gve driver relevant to their networking stack. The source identifies Linux kernel versions including 6.9, 6.12.64, 6.18.4, and 6.19 as affected, but distribution package impact must be confirmed with vendor mapping.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The described failure mode is an interrupt-ordering race causing kernel failures, not a documented remote code execution path. Practical exploitability is unclear from the bundle.

Researcher notes

Evidence is strongest for root cause and fix mechanics, because the bundle includes the kernel resolution text and stable commit references. Evidence is incomplete for severity, attacker requirements, affected distributions, and exploitability. Avoid assuming broader Linux exposure without driver and kernel-version confirmation.

Mitigation direction

  • Identify Linux assets running affected kernel versions and using the gve network driver.
  • Apply Linux kernel or distribution updates that include the referenced stable commits.
  • If no distro package is available, track vendor advisory and maintenance kernel backports.
  • Prioritize systems where network-driver failure could disrupt critical workloads.

Validation and detection

  • Confirm kernel package version against distribution advisories or the referenced stable commits.
  • Check whether the gve driver is built, loaded, or required on each Linux host.
  • Review boot or kernel logs for gve, IRQ, NAPI, or network-driver crash traces.
  • Verify updated kernels include IRQF_NO_AUTOEN behavior for gve interrupt setup.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71156 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1dfc2e46117e5c41037e27e859e75a7518881ee6, 1dfc2e46117e5c41037e27e859e75a7518881ee6, 1dfc2e46117e5c41037e27e859e75a7518881ee6unaffected
LinuxLinux6.9, 0, 6.12.64, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.