PCI/IOV: Fix race between SR-IOV enable/disable and hotplug
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.252, 5.15.202, 6.1.165, 6.12.75, 6.18.16, 6.19.6, 6.6.128
- CVEs
- CVE-2025-40219
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 11:24 UTC · Revision 1
Source evidence
PCI/IOV: Fix race between SR-IOV enable/disable and hotplug
core-osv · Original sourcePublished 4 Dec 2025, 14:50 UTC
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.
osv:CVE-2025-40219
Kernel
Fixed versions: 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6
Complete source record
{
"id": "338f4490a95ee8a484eac9a8d03951c1f8739f91c5130db38f56e79bc27403b9",
"url": "https://osv.dev/vulnerability/CVE-2025-40219",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "PCI/IOV: Fix race between SR-IOV enable/disable and hotplug",
"summary": "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.",
"evidence": "osv:CVE-2025-40219",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.252",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.202",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.165",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.128",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.75",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.16",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-40219",
"aliases": [
"CVE-2025-40219"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "18f9e9d150fccfa747875df6f0a9f606740762b3"
},
{
"fixed": "3cddde484471c602bea04e6f384819d336a1ff84"
},
{
"fixed": "d7673ac466eca37ec3e6b7cc9ccdb06de3304e9b"
},
{
"fixed": "7c37920c96b85ef4255a7acc795e99e63dd38d59"
},
{
"fixed": "1047ca2d816994f31e1475e63e0c0b7825599747"
},
{
"fixed": "97c18f074ff1c12d016a0753072a3afdfa0b9611"
},
{
"fixed": "bea1d373098b22d7142da48750ce5526096425bc"
},
{
"fixed": "f3015627b6e9ddf85cfeaf42405b3c194dde2c36"
},
{
"fixed": "a5338e365c4559d7b4d7356116b0eb95b12e08d5"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-40219.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.10.252"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.202"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.165"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.128"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.75"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.16"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-40219.json"
}
}
],
"modified": "2026-10-28T02:30:28.152795442Z",
"provider": "osv",
"references": [
"https://cert-portal.siemens.com/productcert/html/ssa-019113.html",
"https://cert-portal.siemens.com/productcert/html/ssa-082556.html",
"https://cert-portal.siemens.com/productcert/html/ssa-457936.html",
"https://git.kernel.org/stable/c/1047ca2d816994f31e1475e63e0c0b7825599747",
"https://git.kernel.org/stable/c/3cddde484471c602bea04e6f384819d336a1ff84",
"https://git.kernel.org/stable/c/7c37920c96b85ef4255a7acc795e99e63dd38d59",
"https://git.kernel.org/stable/c/97c18f074ff1c12d016a0753072a3afdfa0b9611",
"https://git.kernel.org/stable/c/a5338e365c4559d7b4d7356116b0eb95b12e08d5",
"https://git.kernel.org/stable/c/bea1d373098b22d7142da48750ce5526096425bc",
"https://git.kernel.org/stable/c/d7673ac466eca37ec3e6b7cc9ccdb06de3304e9b",
"https://git.kernel.org/stable/c/f3015627b6e9ddf85cfeaf42405b3c194dde2c36",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40219.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-40219",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40219.json"
}
},
"related_cves": [
{
"value": "CVE-2025-40219",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 494927,
"published_at": "2025-12-04T14:50:42.996+00:00"
}