LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22116: idpf: check error for register_netdev() on init

In the Linux kernel, the following vulnerability has been resolved: idpf: check error for register_netdev() on init Current init logic ignores the error code from register_netdev(), which will cause WARN_ON() on attempt to unregister it, if there was one, and there is no info for the user that the creation of the netdev failed. WARNING: CPU: 89 PID: 6902 at net/core/dev.c:11512 unregister_netdevice_many_notify+0x211/0x1a10 ... [ 3707.563641] unregister_netdev+0x1c/0x30 [ 3707.563656] idpf_vport_dealloc+0x5cf/0xce0 [idpf] [ 3707.563684] idpf_deinit_task+0xef/0x160 [idpf] [ 3707.563712] idpf_vc_core_deinit+0x84/0x320 [idpf] [ 3707.563739] idpf_remove+0xbf/0x780 [idpf] [ 3707.563769] pci_device_remove+0xab/0x1e0 [ 3707.563786] device_release_driver_internal+0x371/0x530 [ 3707.563803] driver_detach+0xbf/0x180 [ 3707.563816] bus_remove_driver+0x11b/0x2a0 [ 3707.563829] pci_unregister_driver+0x2a/0x250 Introduce an error check and log the vport number and error code. On removal make sure to check VPORT_REG_NETDEV flag prior to calling unregister and free on the netdev. Add local variables for idx, vport_config and netdev for readability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the idpf network driver. A failed network-device registration was ignored during initialization, then cleanup could later try to unregister an unregistered device and trigger a kernel warning. The business impact is unclear from the sources; prioritize systems using affected kernels and this driver.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize cloud, virtualization, or network-intensive hosts using idpf, and fold remediation into the next controlled kernel update window unless vendor guidance raises severity.

Technical view

The idpf driver did not check register_netdev() return status during vport initialization. If registration failed, later teardown could call unregister_netdev() without confirming registration state, producing WARN_ON() in net/core/dev.c. The fix adds error handling, logging, and checks VPORT_REG_NETDEV before unregister/free.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions with the idpf network driver in use. The source bundle lists Linux as affected but does not provide distribution-specific package status, exploit prerequisites, or full version-range semantics.

Exploitation context

No active exploitation is cited, and KEV status is false. The sources describe an error-handling bug during driver initialization and removal, not a public exploit path. Impact beyond kernel warning or cleanup failure is not established in the supplied evidence.

Researcher notes

The supplied record lacks CVSS, CWE, exploitability details, and distribution mapping. Key validation questions are whether idpf is loaded, whether affected kernel branches are deployed, and whether downstream vendors have backported the register_netdev error-handling fix.

Mitigation direction

  • Apply a kernel update containing the referenced stable fixes or a vendor backport.
  • Check Linux distribution advisories for CVE-2025-22116 package status.
  • Prioritize hosts using the idpf driver or related network devices.
  • Avoid direct deploy assumptions; follow normal kernel change and reboot processes.

Validation and detection

  • Inventory running kernel versions on systems using idpf.
  • Confirm installed kernels include the referenced stable commits or vendor backports.
  • Review kernel logs for idpf register_netdev failures or unregister warnings.
  • Test network interface initialization and removal after patching.
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-22116 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
LinuxLinux0fe45467a1041ea3657a7fa3a791c84c104fbd34, 0fe45467a1041ea3657a7fa3a791c84c104fbd34, 0fe45467a1041ea3657a7fa3a791c84c104fbd34unaffected
LinuxLinux6.7, 0, 6.12.80, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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