CVE-2026-43147 — Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV"
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 05703271c3cdcc0f2a8cf6ebdc45892b8ca83520 and < 40f67686a5002c0c322fac918406bbc8d9c2ec2fversion 6.18≥ 6.17.4 and < 6.18≥ 5.4.301 and < 5.5≥ 6.12.54 and < 6.12.75≥ 6.6.113 and < 6.6.128≥ 6.1.157 and < 6.1.165≥ 5.15.195 and < 5.15.202 and 10 more≥ 5.10.246 and < 5.10.252version ee40e5db052d7c6f406fdb95ad639c894c74674cversion 5c1cd7d405e94dc6cb320cc0cc092b74895b6ddf≥ 05703271c3cdcc0f2a8cf6ebdc45892b8ca83520 and < 2fa119c0e5e528453ebae9e70740e8d2d8c0ed5a≥ 05703271c3cdcc0f2a8cf6ebdc45892b8ca83520 and < 58677783c89681871077f50a7042b0c6380c4fd8≥ 53154cd40ccf285f1d1c24367824082061d155bd and < d47f27e145f8bd13f3c230da5e3af29225b4a2f7≥ 36039348bca77828bf06eae41b8f76e38cd15847 and < 639265296fe6ee21b6f00e00ee2bab65f3b07252≥ a24219172456f035d886857e265ca24c85b167c8 and < 83651d37474c762920e345a3a0828f975ca4d732≥ a645ca21de09e3137cbb224fa6c23cca873a1d01 and < 0de341b2365bad430aade0853fe09c2cbe468f59≥ 1e8a80290f964bdbad225221c8a1594c7e01c8fd and < f61cdd7e9b67bb8961b0a81bf294b78343e5db05 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 5.4.301 and < 5.5≥ 6.19 and < 6.19.6≥ 6.17.4 and < 6.18.16≥ 6.12.54 and < 6.12.75≥ 6.6.113 and < 6.6.128≥ 6.1.157 and < 6.1.165≥ 5.15.195 and < 5.15.202≥ 5.10.246 and < 5.10.252 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.10%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 5.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/0de341b2365bad430aade0853fe09c2cbe468f59
- git.kernel.org/stable/c/639265296fe6ee21b6f00e00ee2bab65f3b07252
- git.kernel.org/stable/c/83651d37474c762920e345a3a0828f975ca4d732
- git.kernel.org/stable/c/58677783c89681871077f50a7042b0c6380c4fd8
- git.kernel.org/stable/c/40f67686a5002c0c322fac918406bbc8d9c2ec2f
- git.kernel.org/stable/c/d47f27e145f8bd13f3c230da5e3af29225b4a2f7
- git.kernel.org/stable/c/2fa119c0e5e528453ebae9e70740e8d2d8c0ed5a
- git.kernel.org/stable/c/f61cdd7e9b67bb8961b0a81bf294b78343e5db05
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-43147 is "Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV"", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.