<?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-01T05:16:48.041684+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-45866</id>
    <title>CVE-2026-45866 — serial: caif: fix use-after-free in caif_serial ldisc_close()</title>
    <updated>2026-10-01T05:16:48.043171+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>serial: caif: fix use-after-free in caif_serial ldisc_close()</p>
<p>There is a use-after-free bug in caif_serial where handle_tx() may
access ser-&gt;tty after the tty has been freed.</p>
<p>The race condition occurs between ldisc_close() and packet transmission:</p>
<p>CPU 0 (close)                     CPU 1 (xmit)
    -------------                     ------------
    ldisc_close()
      tty_kref_put(ser-&gt;tty)
      [tty may be freed here]
                     &lt;-- race window --&gt;
                                      caif_xmit()
                                        handle_tx()
                                          tty = ser-&gt;tty  // dangling ptr
                                          tty-&gt;ops-&gt;write() // UAF!
      schedule_work()
        ser_release()
          unregister_netdevice()</p>
<p>The root cause is that tty_kref_put() is called in ldisc_close() while
the network device is still active and can receive packets.</p>
<p>Since ser and tty have a 1:1 binding relationship with consistent
lifecycles (ser is allocated in ldisc_open and freed in ser_release
via unregister_netdevice, and each ser binds exactly one tty), we can
safely defer the tty reference release to ser_release() where the
network device is unregistered.</p>
<p>Fix this by moving tty_kref_put() from ldisc_close() to ser_release(),
after unregister_netdevice(). This ensures the tty reference is held
as long as the network device exists, preventing the UAF.</p>
<p>Not…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-45866"/>
  </entry>
</feed>
