<?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-10-03T21:39:42.960780+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-2026-45918</id>
    <title>CVE-2026-45918 — ovpn: tcp - don't deref NULL sk_socket member after tcp_close()</title>
    <updated>2026-10-03T21:39:42.961907+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: tcp - don't deref NULL sk_socket member after tcp_close()</p>
<p>When deleting a peer in case of keepalive expiration, the peer is
removed from the OpenVPN hashtable and is temporary inserted in a
"release list" for further processing.</p>
<p>This happens in:
ovpn_peer_keepalive_work()
  unlock_ovpn(release_list)</p>
<p>This processing includes detaching from the socket being used to
talk to this peer, by restoring its original proto and socket
ops/callbacks.</p>
<p>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:</p>
<p>tcp_close(sk)
  __tcp_close(sk)
    sock_orphan(sk)
      sk_set_socket(sk, NULL)</p>
<p>The last function call will set sk-&gt;sk_socket to NULL.</p>
<p>When the releasing routine is resumed, ovpn_tcp_socket_detach()
will attempt to dereference sk-&gt;sk_socket to restore its original
ops member. This operation will crash due to sk-&gt;sk_socket being NULL.</p>
<p>Fix this race condition by testing-and-accessing
sk-&gt;sk_socket atomically under sk-&gt;sk_callback_lock.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-45918"/>
  </entry>
</feed>
