<?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-30T02:55:45.685014+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-68393</id>
    <title>CVE-2026-68393 — Bluetooth: hci_sync: extend conn_hash lookup critical sections</title>
    <updated>2026-09-30T02:55:45.697416+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>Bluetooth: hci_sync: extend conn_hash lookup critical sections</p>
<p>Using RCU-protected pointers outside the critical sections without
refcount is incorrect and may result to UAF.</p>
<p>Extend critical section to cover both hci_conn_hash lookup and use of
the returned conn.</p>
<p>Add surrounding rcu_read_lock() also when return value is not used, in
preparation for RCU lockdep requirement to hci_lookup_le_connect().</p>
<p>This avoids concurrent deletion of the conn before we are done
dereferencing it.</p>
<p>Also, make sure to hold hdev-&gt;lock when accessing hdev-&gt;accept_list.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68393"/>
  </entry>
</feed>
