<?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-29T03:33:26.685384+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-38551</id>
    <title>CVE-2025-38551 — virtio-net: fix recursived rtnl_lock() during probe()</title>
    <updated>2026-09-29T03:33:26.700402+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>virtio-net: fix recursived rtnl_lock() during probe()</p>
<p>The deadlock appears in a stack trace like:</p>
<p>virtnet_probe()
    rtnl_lock()
    virtio_config_changed_work()
      netdev_notify_peers()
        rtnl_lock()</p>
<p>It happens if the VMM sends a VIRTIO_NET_S_ANNOUNCE request while the
virtio-net driver is still probing.</p>
<p>The config_work in probe() will get scheduled until virtnet_open() enables
the config change notification via virtio_config_driver_enable().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38551"/>
  </entry>
</feed>
