<?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>Sat, 03 Oct 2026 11:46:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64043 — ovpn: fix race between deleting interface and adding new peer</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64043</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;ovpn: fix race between deleting interface and adding new peer&lt;/p&gt;
&lt;p&gt;While deleting an existing ovpn interface, there is a very
narrow window where adding a new peer via netlink may cause
the netdevice to hang and prevent its unregistration.&lt;/p&gt;
&lt;p&gt;It may happen during ovpn_dellink(), when all existing peers are
freed and the device is queued for deregistration, but a
CMD_PEER_NEW message comes in adding a new peer that takes again
a reference to the netdev.&lt;/p&gt;
&lt;p&gt;At this point there is no way to release the device because we are
under the assumption that all peers were already released.&lt;/p&gt;
&lt;p&gt;Fix the race condition by releasing all peers in ndo_uninit(),
when the netdevice has already been removed from the netdev
list.&lt;/p&gt;
&lt;p&gt;Also ovpn_peer_add() has now an extra check that forces the
function to bail out if the device reg_state is not REGISTERED.
This way any incoming CMD_PEER_NEW racing with the interface
deletion routine will simply stop before adding the peer.&lt;/p&gt;
&lt;p&gt;Note that the above check happens while holding the netdev_lock
to prevent racing netdev state changes.&lt;/p&gt;
&lt;p&gt;ovpn_dellink() is now empty and can be removed.&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;ovpn: fix race between deleting interface and adding new peer&lt;/p&gt;
&lt;p&gt;While deleting an existing ovpn interface, there is a very
narrow window where adding a new peer via netlink may cause
the netdevice to hang and prevent its unregistration.&lt;/p&gt;
&lt;p&gt;It may happen during ovpn_dellink(), when all existing peers are
freed and the device is queued for deregistration, but a
CMD_PEER_NEW message comes in adding a new peer that takes again
a reference to the netdev.&lt;/p&gt;
&lt;p&gt;At this point there is no way to release the device because we are
under the assumption that all peers were already released.&lt;/p&gt;
&lt;p&gt;Fix the race condition by releasing all peers in ndo_uninit(),
when the netdevice has already been removed from the netdev
list.&lt;/p&gt;
&lt;p&gt;Also ovpn_peer_add() has now an extra check that forces the
function to bail out if the device reg_state is not REGISTERED.
This way any incoming CMD_PEER_NEW racing with the interface
deletion routine will simply stop before adding the peer.&lt;/p&gt;
&lt;p&gt;Note that the above check happens while holding the netdev_lock
to prevent racing netdev state changes.&lt;/p&gt;
&lt;p&gt;ovpn_dellink() is now empty and can be removed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64043</guid>
    </item>
  </channel>
</rss>
