VYPR
Unrated severityNVD Advisory· Published Dec 4, 2025· Updated Apr 15, 2026

CVE-2025-40219

CVE-2025-40219

Description

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

PCI/IOV: Fix race between SR-IOV enable/disable and hotplug

Commit 05703271c3cd ("PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV") tried to fix a race between the VF removal inside sriov_del_vfs() and concurrent hot unplug by taking the PCI rescan/remove lock in sriov_del_vfs(). Similarly the PCI rescan/remove lock was also taken in sriov_add_vfs() to protect addition of VFs.

This approach however causes deadlock on trying to remove PFs with SR-IOV enabled because PFs disable SR-IOV during removal and this removal happens under the PCI rescan/remove lock. So the original fix had to be reverted.

Instead of taking the PCI rescan/remove lock in sriov_add_vfs() and sriov_del_vfs(), fix the race that occurs with SR-IOV enable and disable vs hotplug higher up in the callchain by taking the lock in sriov_numvfs_store() before calling into the driver's sriov_configure() callback.

AI Insight

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

In the Linux kernel, a race condition in PCI/IOV between SR-IOV enable/disable and hotplug was fixed by moving lock acquisition to prevent deadlock.

Vulnerability

Analysis

CVE-2025-40219 describes a race condition in the Linux kernel's PCI/IOV subsystem. The bug occurs between SR-IOV enable/disable operations and hot plug events. A previous fix attempt (commit 05703271c3cd) took the PCI rescan-remove lock in sriov_del_vfs() and sriov_add_vfs(), but this caused a deadlock when removing a PF with SR-IOV enabled because PF removal already holds that lock.

Exploitation

The race can be triggered by an attacker with local access who can concurrently initiate SR-IOV configuration changes (e.g., writing to sriov_numvfs) and hot unplug or hot add events. No special privileges beyond the ability to manage PCI devices are required, though the attack surface is limited to systems with SR-IOV capable hardware.

Impact

A successful exploit may lead to use-after-free or other memory corruption, resulting in system crashes or potential privilege escalation. The exact impact depends on the driver and hardware, but the vulnerability is classified with a CVSS score indicating moderate severity.

Mitigation

The fix is included in Linux kernel stable updates. It moves the lock acquisition from sriov_add_vfs() and sriov_del_vfs() to sriov_numvfs_store(), acquiring the PCI rescan-remove lock before calling the driver's sriov_configure() callback. Users should apply the latest kernel patches to mitigate this vulnerability.

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

Affected products

2

Patches

8

Vulnerability mechanics

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

References

8

News mentions

0

No linked articles in our index yet.