<?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>Fri, 02 Oct 2026 13:50:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49434 — PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49434</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;PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()&lt;/p&gt;
&lt;p&gt;The sysfs sriov_numvfs_store() path acquires the device lock before the
config space access lock:&lt;/p&gt;
&lt;p&gt;sriov_numvfs_store
    device_lock                 # A (1) acquire device lock
    sriov_configure
      vfio_pci_sriov_configure  # (for example)
        vfio_pci_core_sriov_configure
          pci_disable_sriov
            sriov_disable
              pci_cfg_access_lock
                pci_wait_cfg    # B (4) wait for dev-&amp;gt;block_cfg_access == 0&lt;/p&gt;
&lt;p&gt;Previously, pci_dev_lock() acquired the config space access lock before the
device lock:&lt;/p&gt;
&lt;p&gt;pci_dev_lock
    pci_cfg_access_lock
      dev-&amp;gt;block_cfg_access = 1 # B (2) set dev-&amp;gt;block_cfg_access = 1
    device_lock                 # A (3) wait for device lock&lt;/p&gt;
&lt;p&gt;Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may
deadlock with sriov_numvfs_store() if the operations occur in the sequence
(1) (2) (3) (4).&lt;/p&gt;
&lt;p&gt;Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires
the device lock before the config space access lock, the same as the
sriov_numvfs_store() path.&lt;/p&gt;
&lt;p&gt;[bhelgaas: combined and adapted commit log from Jay Zhou&amp;#39;s independent
subsequent posting:
https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]&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;PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()&lt;/p&gt;
&lt;p&gt;The sysfs sriov_numvfs_store() path acquires the device lock before the
config space access lock:&lt;/p&gt;
&lt;p&gt;sriov_numvfs_store
    device_lock                 # A (1) acquire device lock
    sriov_configure
      vfio_pci_sriov_configure  # (for example)
        vfio_pci_core_sriov_configure
          pci_disable_sriov
            sriov_disable
              pci_cfg_access_lock
                pci_wait_cfg    # B (4) wait for dev-&amp;gt;block_cfg_access == 0&lt;/p&gt;
&lt;p&gt;Previously, pci_dev_lock() acquired the config space access lock before the
device lock:&lt;/p&gt;
&lt;p&gt;pci_dev_lock
    pci_cfg_access_lock
      dev-&amp;gt;block_cfg_access = 1 # B (2) set dev-&amp;gt;block_cfg_access = 1
    device_lock                 # A (3) wait for device lock&lt;/p&gt;
&lt;p&gt;Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may
deadlock with sriov_numvfs_store() if the operations occur in the sequence
(1) (2) (3) (4).&lt;/p&gt;
&lt;p&gt;Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires
the device lock before the config space access lock, the same as the
sriov_numvfs_store() path.&lt;/p&gt;
&lt;p&gt;[bhelgaas: combined and adapted commit log from Jay Zhou&amp;#39;s independent
subsequent posting:
https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49434</guid>
    </item>
  </channel>
</rss>
