<?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-07T12:11:58.744542+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-52502</id>
    <title>CVE-2023-52502 — net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()</title>
    <updated>2026-10-07T12:11:58.789944+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>net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn()</p>
<p>Sili Luo reported a race in nfc_llcp_sock_get(), leading to UAF.</p>
<p>Getting a reference on the socket found in a lookup while
holding a lock should happen before releasing the lock.</p>
<p>nfc_llcp_sock_get_sn() has a similar problem.</p>
<p>Finally nfc_llcp_recv_snl() needs to make sure the socket
found by nfc_llcp_sock_from_sn() does not disappear.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-52502"/>
  </entry>
</feed>
