CVE-2025-71156 [High] | Security Vulnerability in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-01-24	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-01-24

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2025-71156

vendor	priority	summary	link
`debian`	unimportant	CVE-2025-71156 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-71156
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-71156
`suse`	medium	CVE-2025-71156 severity moderate: SUSE including 372 source package names (13.2-9.1:libsqlite3-0-3.49.1-1.1, 2.1.3-6.31:libsqlite3-0-3.49.1-1.1, …), 680 product×package rows across 80 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (80 product lines)): Fixed 238, Known Affected 231, Known Not Affected 186, First Fixed 25.	https://www.suse.com/security/cve/CVE-2025-71156/
`ubuntu`	medium	CVE-2025-71156 medium priority: Ubuntu including 157 source packages (linux, linux-allwinner-5.19, …), 1256 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): DNE 871, ignored 169, not-affected 112, released 88, pending 11, needed 5.	https://ubuntu.com/security/CVE-2025-71156

Affected software / configurations for CVE-2025-71156

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.9, < 6.12.64	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.13, < 6.18.4	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.19	cpe:2.3:o:linux:linux_kernel:6.19:rc1::::::
linux	linux_kernel	6.19	cpe:2.3:o:linux:linux_kernel:6.19:rc2::::::
linux	linux_kernel	6.19	cpe:2.3:o:linux:linux_kernel:6.19:rc3::::::

References for CVE-2025-71156

URL	Tags
https://git.kernel.org/stable/c/3d970eda003441f66551a91fda16478ac0711617	Patch
https://git.kernel.org/stable/c/48f9277680925e1a8623d6b2c50aadb7af824ace	Patch
https://git.kernel.org/stable/c/f5b7f49bd2377916ad57cbd1210c61196daff013	Patch

URL

CVE-2025-71156 | gve: defer interrupt enabling until NAPI registration

Exploit prediction scoring system (EPSS) score for CVE-2025-71156

Common vulnerability scoring system (CVSS) metrics for CVE-2025-71156

Weakness enumeration for CVE-2025-71156

OS Trackers for CVE-2025-71156

Affected software / configurations for CVE-2025-71156

References for CVE-2025-71156