CVE-2026-43147

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-06. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 > /sys/bus/pci/devices//sriov_numvfs $ echo 1 > /sys/bus/pci/devices//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 v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 13, 2026

Advisory Details (8)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f61cdd7e9b67bb8961b0a81bf294b78343e5db05
generic

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d47f27e145f8bd13f3c230da5e3af29225b4a2f7
generic

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83651d37474c762920e345a3a0828f975ca4d732
generic

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/639265296fe6ee21b6f00e00ee2bab65f3b07252
generic

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58677783c89681871077f50a7042b0c6380c4fd8
generic

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40f67686a5002c0c322fac918406bbc8d9c2ec2f
generic

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2fa119c0e5e528453ebae9e70740e8d2d8c0ed5a
generic

Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0de341b2365bad430aade0853fe09c2cbe468f59

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-134.134.1~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
linuxKernel @ 5.10.252—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 176 total refreshes for this CVE.

  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-11 16:23 UTCOSV refresh
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-23 20:13 UTCEG score recompute
  17. 2026-08-23 20:13 UTCVendor advisory
  18. 2026-08-23 20:13 UTCGHSA enrichment
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 12:58 UTCEG score recompute
  25. 2026-08-17 12:58 UTCVendor advisory
Show 75 more
  1. 2026-08-17 12:58 UTCGHSA enrichment
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 04:54 UTCEG score recompute
  4. 2026-08-16 04:54 UTCVendor advisory
  5. 2026-08-16 04:54 UTCGHSA enrichment
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:54 UTCVendor advisory
  8. 2026-08-15 01:54 UTCGHSA enrichment
  9. 2026-08-14 03:29 UTCEG score recompute
  10. 2026-08-14 03:29 UTCVendor advisory
  11. 2026-08-14 03:29 UTCGHSA enrichment
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-12 22:22 UTCEG score recompute
  14. 2026-08-12 22:22 UTCVendor advisory
  15. 2026-08-12 22:22 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-11 23:57 UTCEG score recompute
  18. 2026-08-11 23:57 UTCVendor advisory
  19. 2026-08-11 23:57 UTCGHSA enrichment
  20. 2026-08-11 13:43 UTCEPSS rescore
  21. 2026-08-11 01:33 UTCEG score recompute
  22. 2026-08-11 01:33 UTCVendor advisory
  23. 2026-08-11 01:33 UTCGHSA enrichment
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 01:01 UTCEG score recompute
  26. 2026-08-10 01:01 UTCVendor advisory
  27. 2026-08-10 01:01 UTCGHSA enrichment
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 02:36 UTCEG score recompute
  30. 2026-08-09 02:36 UTCVendor advisory
  31. 2026-08-09 02:36 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-07 19:11 UTCEG score recompute
  34. 2026-08-07 19:11 UTCVendor advisory
  35. 2026-08-07 19:11 UTCGHSA enrichment
  36. 2026-08-06 20:46 UTCEG score recompute
  37. 2026-08-06 20:46 UTCVendor advisory
  38. 2026-08-06 20:46 UTCGHSA enrichment
  39. 2026-08-06 13:46 UTCEPSS rescore
  40. 2026-08-05 22:22 UTCEG score recompute
  41. 2026-08-05 22:22 UTCVendor advisory
  42. 2026-08-05 22:22 UTCGHSA enrichment
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 10:38 UTCEPSS rescore
  46. 2026-08-04 02:23 UTCEG score recompute
  47. 2026-08-04 02:23 UTCVendor advisory
  48. 2026-08-04 02:23 UTCGHSA enrichment
  49. 2026-08-03 10:36 UTCEPSS rescore
  50. 2026-08-03 03:59 UTCVendor advisory
  51. 2026-08-03 03:59 UTCGHSA enrichment
  52. 2026-08-02 05:09 UTCEG score recompute
  53. 2026-08-02 05:09 UTCVendor advisory
  54. 2026-08-02 05:09 UTCGHSA enrichment
  55. 2026-08-02 02:27 UTCEPSS rescore
  56. 2026-08-01 04:16 UTCEPSS rescore
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-28 15:36 UTCEPSS rescore
  59. 2026-07-27 14:13 UTCEPSS rescore
  60. 2026-07-26 14:54 UTCEPSS rescore
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-24 14:17 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 03:13 UTCEG score recompute
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-20 22:02 UTCOSV refresh
  68. 2026-07-20 17:08 UTCEPSS rescore
  69. 2026-07-19 14:31 UTCEPSS rescore
  70. 2026-07-16 17:03 UTCEPSS rescore
  71. 2026-07-15 16:57 UTCEPSS rescore
  72. 2026-07-15 02:00 UTCEPSS rescore
  73. 2026-07-13 22:30 UTCEPSS rescore
  74. 2026-07-13 06:13 UTCEPSS rescore
  75. 2026-07-12 05:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43147?
CVE-2026-43147 is a medium vulnerability published on May 6, 2026. 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…
When was CVE-2026-43147 disclosed?
CVE-2026-43147 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43147 actively exploited?
CVE-2026-43147 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.3% of all scored CVEs.
What is the CVSS score of CVE-2026-43147?
CVE-2026-43147 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43147?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43147, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43147

Explore →

Is Your Infrastructure Affected by CVE-2026-43147?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs