<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-03T04:31:58.254518+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-98604</id>
    <title>CVE-2026-98604 — ovpn: replace bind when learning local endpoint</title>
    <updated>2026-11-03T04:31:58.256009+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>ovpn: replace bind when learning local endpoint</p>
<p>struct ovpn_bind is published through peer-&gt;bind with RCU, but local
endpoint learning updates bind-&gt;local in place under peer-&gt;lock. UDP TX
reads the field without that lock. In particular, a concurrent IPv6
update can therefore result in a torn address read.</p>
<p>Use ovpn_peer_reset_sockaddr to publish a replacement bind when learning
a new local endpoint, just as a remote endpoint change does. Preserve
the current remote address and reset the dst cache only after the new
bind has been published successfully.</p>
<p>Track remote endpoint changes separately so that float notification and
transport-address rehashing remain limited to actual peer floats.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98604"/>
  </entry>
</feed>
