Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2025-39911

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path If request_irq() in i40e_vsi_request_irq_msix() fails in an itera…

Published Oct 1, 2025EPSS 0.16%

Overview

CVE-2025-39911 is a high-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path

If request_irq() in i40e_vsi_request_irq_msix() fails in an iteration

later than the first, the error path wants to free the IRQs requested

so far. However, it uses the wrong dev_id argument for free_irq(), so

it does not free the IRQs correctly and instead triggers the warning:

Trying to free already-free IRQ 173

WARNING: CPU: 25 PID: 1091 at kernel/irq/manage.c:1829 __free_irq+0x192/0x2c0

Modules linked in: i40e(+) [...]

CPU: 25 UID: 0 PID: 1091 Comm: NetworkManager Not tainted 6.17.0-rc1+ #1 PREEMPT(lazy)

Hardware name: [...]

RIP: 0010:__free_irq+0x192/0x2c0

[...]

Call Trace:

<TASK>

free_irq+0x32/0x70

i40e_vsi_request_irq_msix.cold+0x63/0x8b [i40e]

i40e_vsi_request_irq+0x79/0x80 [i40e]

i40e_vsi_open+0x21f/0x2f0 [i40e]

i40e_open+0x63/0x130 [i40e]

__dev_open+0xfc/0x210

__dev_change_flags+0x1fc/0x240

netif_change_flags+0x27/0x70

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/13ab9adef3cd386511c930a9660ae06595007f89Refgit.kernel.org/stable/c/23431998a37764c464737b855c71a81d50992e98Refgit.kernel.org/stable/c/6e4016c0dca53afc71e3b99e24252b63417395dfRefgit.kernel.org/stable/c/915470e1b44e71d1dd07ee067276f003c3521ee3Refgit.kernel.org/stable/c/a30afd6617c30aaa338d1dbcb1e34e7a1890085cRefgit.kernel.org/stable/c/b905b2acb3a0bbb08ad9be9984d8cdabdf827315Refgit.kernel.org/stable/c/b9721a023df38cf44a88f2739b4cf51efd051f85Refgit.kernel.org/stable/c/c62580674ce5feb1be4f90b5873ff3ce50e0a1dbReflists.debian.org/debian-lts-announce/2025/10/msg00008.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-39911?

CVE-2025-39911 is a high-severity vulnerability. It was published on October 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-39911?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-39911?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-39911?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-39911 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999