<?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 21:39:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45918 — ovpn: tcp - don't deref NULL sk_socket member after tcp_close()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-45918</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: tcp - don&amp;#39;t deref NULL sk_socket member after tcp_close()&lt;/p&gt;
&lt;p&gt;When deleting a peer in case of keepalive expiration, the peer is
removed from the OpenVPN hashtable and is temporary inserted in a
&amp;#34;release list&amp;#34; for further processing.&lt;/p&gt;
&lt;p&gt;This happens in:
ovpn_peer_keepalive_work()
  unlock_ovpn(release_list)&lt;/p&gt;
&lt;p&gt;This processing includes detaching from the socket being used to
talk to this peer, by restoring its original proto and socket
ops/callbacks.&lt;/p&gt;
&lt;p&gt;In case of TCP it may happen that, while the peer is sitting in
the release list, userspace decides to close the socket.
This will result in a concurrent execution of:&lt;/p&gt;
&lt;p&gt;tcp_close(sk)
  __tcp_close(sk)
    sock_orphan(sk)
      sk_set_socket(sk, NULL)&lt;/p&gt;
&lt;p&gt;The last function call will set sk-&amp;gt;sk_socket to NULL.&lt;/p&gt;
&lt;p&gt;When the releasing routine is resumed, ovpn_tcp_socket_detach()
will attempt to dereference sk-&amp;gt;sk_socket to restore its original
ops member. This operation will crash due to sk-&amp;gt;sk_socket being NULL.&lt;/p&gt;
&lt;p&gt;Fix this race condition by testing-and-accessing
sk-&amp;gt;sk_socket atomically under sk-&amp;gt;sk_callback_lock.&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: tcp - don&amp;#39;t deref NULL sk_socket member after tcp_close()&lt;/p&gt;
&lt;p&gt;When deleting a peer in case of keepalive expiration, the peer is
removed from the OpenVPN hashtable and is temporary inserted in a
&amp;#34;release list&amp;#34; for further processing.&lt;/p&gt;
&lt;p&gt;This happens in:
ovpn_peer_keepalive_work()
  unlock_ovpn(release_list)&lt;/p&gt;
&lt;p&gt;This processing includes detaching from the socket being used to
talk to this peer, by restoring its original proto and socket
ops/callbacks.&lt;/p&gt;
&lt;p&gt;In case of TCP it may happen that, while the peer is sitting in
the release list, userspace decides to close the socket.
This will result in a concurrent execution of:&lt;/p&gt;
&lt;p&gt;tcp_close(sk)
  __tcp_close(sk)
    sock_orphan(sk)
      sk_set_socket(sk, NULL)&lt;/p&gt;
&lt;p&gt;The last function call will set sk-&amp;gt;sk_socket to NULL.&lt;/p&gt;
&lt;p&gt;When the releasing routine is resumed, ovpn_tcp_socket_detach()
will attempt to dereference sk-&amp;gt;sk_socket to restore its original
ops member. This operation will crash due to sk-&amp;gt;sk_socket being NULL.&lt;/p&gt;
&lt;p&gt;Fix this race condition by testing-and-accessing
sk-&amp;gt;sk_socket atomically under sk-&amp;gt;sk_callback_lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-45918</guid>
    </item>
  </channel>
</rss>
