<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 19:50:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43147 — Revert "PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV"</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43147</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Revert &amp;#34;PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV&amp;#34;&lt;/p&gt;
&lt;p&gt;This reverts commit 05703271c3cd (&amp;#34;PCI/IOV: Add PCI rescan-remove locking
when enabling/disabling SR-IOV&amp;#34;), 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:&lt;/p&gt;
&lt;p&gt;$ echo &amp;lt;NUM&amp;gt; &amp;gt; /sys/bus/pci/devices/&amp;lt;pf&amp;gt;/sriov_numvfs
  $ echo 1 &amp;gt; /sys/bus/pci/devices/&amp;lt;pf&amp;gt;/remove&lt;/p&gt;
&lt;p&gt;A trimmed trace of the deadlock on a mlx5 device is as below:&lt;/p&gt;
&lt;p&gt;zsh/5715 is trying to acquire lock:
  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140&lt;/p&gt;
&lt;p&gt;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:
   [&amp;lt;00000259778c4f90&amp;gt;] dump_stack_lvl+0xc0/0x110
   [&amp;lt;00000259779c844e&amp;gt;] print_deadlock_bug+0x31e/0x330
   [&amp;lt;00000259779c1908&amp;gt;] __lock_acquire+0x16c8/0x32f0
   [&amp;lt;00000259779bffac&amp;gt;] lock_acquire+0x14c/0x350
   [&amp;lt;00000259789643a6&amp;gt;] __mutex_lock_common+0xe6/0x1520
   [&amp;lt;000002597896413c&amp;gt;] mutex_lock_nested+0x3c/0x50
   [&amp;lt;00000259784a07e4&amp;gt;] sriov_disable+0x34/0x140
   [&amp;lt;00000258f7d6dd80&amp;gt;] mlx5_sriov_disable+0x50/0x80 [mlx5_core]
   [&amp;lt;00000258f7d5745e&amp;gt;] remove_one+0x5e/0xf0 [mlx5_core]
   [&amp;lt;00000259784857fc&amp;gt;] pci_device_remove+0x3c/0xa0
   [&amp;lt;000002597851012e&amp;gt;] device_release_driver_int…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Revert &amp;#34;PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV&amp;#34;&lt;/p&gt;
&lt;p&gt;This reverts commit 05703271c3cd (&amp;#34;PCI/IOV: Add PCI rescan-remove locking
when enabling/disabling SR-IOV&amp;#34;), 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:&lt;/p&gt;
&lt;p&gt;$ echo &amp;lt;NUM&amp;gt; &amp;gt; /sys/bus/pci/devices/&amp;lt;pf&amp;gt;/sriov_numvfs
  $ echo 1 &amp;gt; /sys/bus/pci/devices/&amp;lt;pf&amp;gt;/remove&lt;/p&gt;
&lt;p&gt;A trimmed trace of the deadlock on a mlx5 device is as below:&lt;/p&gt;
&lt;p&gt;zsh/5715 is trying to acquire lock:
  000002597926ef50 (pci_rescan_remove_lock){+.+.}-{3:3}, at: sriov_disable+0x34/0x140&lt;/p&gt;
&lt;p&gt;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:
   [&amp;lt;00000259778c4f90&amp;gt;] dump_stack_lvl+0xc0/0x110
   [&amp;lt;00000259779c844e&amp;gt;] print_deadlock_bug+0x31e/0x330
   [&amp;lt;00000259779c1908&amp;gt;] __lock_acquire+0x16c8/0x32f0
   [&amp;lt;00000259779bffac&amp;gt;] lock_acquire+0x14c/0x350
   [&amp;lt;00000259789643a6&amp;gt;] __mutex_lock_common+0xe6/0x1520
   [&amp;lt;000002597896413c&amp;gt;] mutex_lock_nested+0x3c/0x50
   [&amp;lt;00000259784a07e4&amp;gt;] sriov_disable+0x34/0x140
   [&amp;lt;00000258f7d6dd80&amp;gt;] mlx5_sriov_disable+0x50/0x80 [mlx5_core]
   [&amp;lt;00000258f7d5745e&amp;gt;] remove_one+0x5e/0xf0 [mlx5_core]
   [&amp;lt;00000259784857fc&amp;gt;] pci_device_remove+0x3c/0xa0
   [&amp;lt;000002597851012e&amp;gt;] device_release_driver_int…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43147</guid>
    </item>
  </channel>
</rss>
