VYPR
← All advisories
Medium severity5.5NVD Advisory· Published Apr 16, 2025· Updated Apr 2, 2026

CVE-2025-22116

CVE-2025-22116

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Missing error check for register_netdev() in Linux kernel idpf driver can trigger WARN_ON on unregister, leading to denial of service.

The vulnerability lies in the idpf network driver in the Linux kernel. During initialization, the function register_netdev() is called without checking its return value. If this call fails (e.g., due to resource exhaustion), the netdev is not properly registered, but the driver continues as if successful [1]. This oversight can lead to a kernel warning when the driver attempts to unregister the device later.

Exploitation requires local access to trigger the failure condition of register_netdev(), but the lack of error handling means any such failure will go unnoticed. On driver removal, the unregister path calls unregister_netdev() on a device that was never registered, causing a WARN_ON in the kernel and potentially a system crash [1]. The warning trace shows the call sequence leading to the panic.

The impact is a denial of service due to kernel warning messages and possible system instability. An attacker with local access could potentially cause repeated failures to exhaust resources and trigger the bug. However, no code execution or privilege escalation is implied.

The fix introduces an error check for register_netdev(), logs the failure with the vport number and error code, and ensures that the unregister and free steps are only performed if the VPORT_REG_NETDEV flag is set [1]. Users should apply the committed patches from kernel.org stable branches to remediate the issue.

References
  1. Making sure you're not a bot!

AI Insight generated on May 20, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

91

Patches

2
89768e337522
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.gitvia osv
commit
680811c67906
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.gitvia osv
commit

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

3

News mentions

0

No linked articles in our index yet.