Medium 5.5Published May 6, 2026

CVE-2026-43147Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV"

Updated under an hour ago (Oct 26, 2026, 7:30 PM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" This reverts commit 05703271c3cd ("PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV"), which causes a deadlock by recursively taking pci_rescan_remove_lock when sriov_del_vfs() is called as part of pci_stop_and_remove_bus_device(). For example with the following sequence of commands: $ echo <NUM> > /sys/bus/pci/devices/<pf>/sriov_numvfs $ echo 1 > /sys/bus/pci/devices/<pf>/remove A trimmed trace of the deadlock on a mlx5 device is as below: zsh/5715 is trying to acquire lock: 000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140 but task is already holding lock: 000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_stop_and_remove_bus_device_locked+0x24/0x80 ... Call Trace: [<00000259778c4f90>] dump_stack_lvl+0xc0/0x110 [<00000259779c844e>] print_deadlock_bug+0x31e/0x330 [<00000259779c1908>] __lock_acquire+0x16c8/0x32f0 [<00000259779bffac>] lock_acquire+0x14c/0x350 [<00000259789643a6>] __mutex_lock_common+0xe6/0x1520 [<000002597896413c>] mutex_lock_nested+0x3c/0x50 [<00000259784a07e4>] sriov_disable+0x34/0x140 [<00000258f7d6dd80>] mlx5_sriov_disable+0x50/0x80 [mlx5_core] [<00000258f7d5745e>] remove_one+0x5e/0xf0 [mlx5_core] [<00000259784857fc>] pci_device_remove+0x3c/0xa0 [<000002597851012e>] device_release_driver_internal+0x18e/0x280 [<000002597847ae22>] pci_stop_bus_device+0x82/0xa0 [<000002597847afce>] pci_stop_and_remove_bus_device_locked+0x5e/0x80 [<00000259784972c2>] remove_store+0x72/0x90 [<0000025977e6661a>] kernfs_fop_write_iter+0x15a/0x200 [<0000025977d7241c>] vfs_write+0x24c/0x300 [<0000025977d72696>] ksys_write+0x86/0x110 [<000002597895b61c>] __do_syscall+0x14c/0x400 [<000002597896e0ee>] system_call+0x6e/0x90 This alone is not a complete fix as it restores the issue the cited commit tried to solve. A new fix will be provided as a follow on.

CVSS: 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: May 23, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 1e8a80290f964bdbad225221c8a1594c7e01c8fd before f61cdd7e9b67bb8961b0a81bf294b78343e5db05; from a645ca21de09e3137cbb224fa6c23cca873a1d01 before 0de341b2365bad430aade0853fe09c2cbe468f59; from a24219172456f035d886857e265ca24c85b167c8 before 83651d37474c762920e345a3a0828f975ca4d732; from 36039348bca77828bf06eae41b8f76e38cd15847 before 639265296fe6ee21b6f00e00ee2bab65f3b07252; from 53154cd40ccf285f1d1c24367824082061d155bd before d47f27e145f8bd13f3c230da5e3af29225b4a2f7; 05703271c3cdcc0f2a8cf6ebdc45892b8ca83520 builds before 40f67686a5002c0c322fac918406bbc8d9c2ec2f; from 05703271c3cdcc0f2a8cf6ebdc45892b8ca83520 before 58677783c89681871077f50a7042b0c6380c4fd8; 05703271c3cdcc0f2a8cf6ebdc45892b8ca83520 builds before 2fa119c0e5e528453ebae9e70740e8d2d8c0ed5a; and 9 more ranges	CNA record
linux linux_kernel linux:linux_kernel	from 5.4.301 before 5.5; from 5.10.246 before 5.10.252; from 5.15.195 before 5.15.202; from 6.1.157 before 6.1.165; from 6.6.113 before 6.6.128; from 6.12.54 before 6.12.75; from 6.17.4 before 6.18.16; from 6.19 before 6.19.6	NVD

References

References

https://git.kernel.org/stable/c/f61cdd7e9b67bb8961b0a81bf294b78343e5db05	patch
https://git.kernel.org/stable/c/0de341b2365bad430aade0853fe09c2cbe468f59	patch
https://git.kernel.org/stable/c/83651d37474c762920e345a3a0828f975ca4d732	patch
https://git.kernel.org/stable/c/639265296fe6ee21b6f00e00ee2bab65f3b07252	patch
https://git.kernel.org/stable/c/d47f27e145f8bd13f3c230da5e3af29225b4a2f7	patch
https://git.kernel.org/stable/c/40f67686a5002c0c322fac918406bbc8d9c2ec2f	patch
https://git.kernel.org/stable/c/58677783c89681871077f50a7042b0c6380c4fd8	patch
https://git.kernel.org/stable/c/2fa119c0e5e528453ebae9e70740e8d2d8c0ed5a	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.