Kernel warning via mismatched IRQ cleanup identifier
Published Oct 1, 2025 · Updated Jun 11, 2026
Resource-management flaw in the Linux i40e driver allows local users with elevated privileges to trigger an IRQ warning. In i40e_vsi_request_irq_msix(), a later request_irq() failure sends free_irq() a dev_id different from the one used for registration, so requested IRQs remain allocated while cleanup targets the wrong entry. Reaching the error path requires CAP_NET_ADMIN in the initial namespace and a physical i40e NIC; the documented result is a kernel warning during interface activation.
Summary
What happened
Resource-management flaw in the Linux i40e driver allows local users with elevated privileges to trigger an IRQ warning. In i40e_vsi_request_irq_msix(), a later request_irq() failure sends free_irq() a dev_id different from the one used for registration, so requested IRQs remain allocated while cleanup targets the wrong entry. Reaching the error path requires CAP_NET_ADMIN in the initial namespace and a physical i40e NIC; the documented result is a kernel warning during interface activation.
The record
- CVE
- CVE-2025-39911
- Published
- Oct 1, 2025
- Updated
- Jun 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.13
- Affected versionversion=493fb30011b3ab5173cef96f1d1ce126da051792 <13ab9adef3cd386511c930a9660ae06595007f89
- Affected versionversion=493fb30011b3ab5173cef96f1d1ce126da051792 <23431998a37764c464737b855c71a81d50992e98
- Affected versionversion=493fb30011b3ab5173cef96f1d1ce126da051792 <6e4016c0dca53afc71e3b99e24252b63417395df
- Affected versionversion=493fb30011b3ab5173cef96f1d1ce126da051792 <915470e1b44e71d1dd07ee067276f003c3521ee3
- Affected versionversion=493fb30011b3ab5173cef96f1d1ce126da051792 <a30afd6617c30aaa338d1dbcb1e34e7a1890085c
- Affected versionversion=493fb30011b3ab5173cef96f1d1ce126da051792 <b905b2acb3a0bbb08ad9be9984d8cdabdf827315
- Affected versionversion=493fb30011b3ab5173cef96f1d1ce126da051792 <b9721a023df38cf44a88f2739b4cf51efd051f85
- Affected versionversion=493fb30011b3ab5173cef96f1d1ce126da051792 <c62580674ce5feb1be4f90b5873ff3ce50e0a1db
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo