<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T04:49:03.418236+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-38720</id>
    <title>CVE-2025-38720 — net: hibmcge: fix rtnl deadlock issue</title>
    <updated>2026-09-30T04:49:03.420646+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: hibmcge: fix rtnl deadlock issue</p>
<p>Currently, the hibmcge netdev acquires the rtnl_lock in
pci_error_handlers.reset_prepare() and releases it in
pci_error_handlers.reset_done().</p>
<p>However, in the PCI framework:
pci_reset_bus - __pci_reset_slot - pci_slot_save_and_disable_locked -
 pci_dev_save_and_disable - err_handler-&gt;reset_prepare(dev);</p>
<p>In pci_slot_save_and_disable_locked():
	list_for_each_entry(dev, &amp;slot-&gt;bus-&gt;devices, bus_list) {
		if (!dev-&gt;slot || dev-&gt;slot!= slot)
			continue;
		pci_dev_save_and_disable(dev);
		if (dev-&gt;subordinate)
			pci_bus_save_and_disable_locked(dev-&gt;subordinate);
	}</p>
<p>This will iterate through all devices under the current bus and execute
err_handler-&gt;reset_prepare(), causing two devices of the hibmcge driver
to sequentially request the rtnl_lock, leading to a deadlock.</p>
<p>Since the driver now executes netif_device_detach()
before the reset process, it will not concurrently with
other netdev APIs, so there is no need to hold the rtnl_lock now.</p>
<p>Therefore, this patch removes the rtnl_lock during the reset process and
adjusts the position of HBG_NIC_STATE_RESETTING to ensure
that multiple resets are not executed concurrently.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38720"/>
  </entry>
</feed>
