<?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-29T05:28:16.794843+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-2023-53020</id>
    <title>CVE-2023-53020 — l2tp: close all race conditions in l2tp_tunnel_register()</title>
    <updated>2026-09-29T05:28:16.795897+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>l2tp: close all race conditions in l2tp_tunnel_register()</p>
<p>The code in l2tp_tunnel_register() is racy in several ways:</p>
<p>1. It modifies the tunnel socket _after_ publishing it.</p>
<p>2. It calls setup_udp_tunnel_sock() on an existing socket without
   locking.</p>
<p>3. It changes sock lock class on fly, which triggers many syzbot
   reports.</p>
<p>This patch amends all of them by moving socket initialization code
before publishing and under sock lock. As suggested by Jakub, the
l2tp lockdep class is not necessary as we can just switch to
bh_lock_sock_nested().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-53020"/>
  </entry>
</feed>
