Strix
26.1K

CVE-2025-40219

UnknownEPSS 0.17%

Last modified

CVE-2025-40219 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

6.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 18f9e9d150fccfa747875df6f0a9f606740762b3, < 3cddde484471c602bea04e6f384819d336a1ff84; >= 18f9e9d150fccfa747875df6f0a9f606740762b3, < d7673ac466eca37ec3e6b7cc9ccdb06de3304e9b; >= 18f9e9d150fccfa747875df6f0a9f606740762b3, < 7c37920c96b85ef4255a7acc795e99e63dd38d59; >= 18f9e9d150fccfa747875df6f0a9f606740762b3, < 1047ca2d816994f31e1475e63e0c0b7825599747; >= 18f9e9d150fccfa747875df6f0a9f606740762b3, < 97c18f074ff1c12d016a0753072a3afdfa0b9611; >= 18f9e9d150fccfa747875df6f0a9f606740762b3, < bea1d373098b22d7142da48750ce5526096425bc; >= 18f9e9d150fccfa747875df6f0a9f606740762b3, < f3015627b6e9ddf85cfeaf42405b3c194dde2c36; >= 18f9e9d150fccfa747875df6f0a9f606740762b3, < a5338e365c4559d7b4d7356116b0eb95b12e08d5
LinuxLinux5.0

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-40219?
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.
How severe is CVE-2025-40219?
Severity scoring for CVE-2025-40219 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2025-40219?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

View all 2025CVEs →

Are you affected by CVE-2025-40219?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST