<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 14:03:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90057 — slip: remove slip_hangup() to fix use-after-free in slip_receive_buf()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90057</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;slip: remove slip_hangup() to fix use-after-free in slip_receive_buf()&lt;/p&gt;
&lt;p&gt;Jaeyoung Chung and Eulgyu Kim reported a slab-use-after-free read
in slip_receive_buf() when racing against tty hangup.&lt;/p&gt;
&lt;p&gt;tty_ldisc_hangup() calls ld-&amp;gt;ops-&amp;gt;hangup() while holding only
a read lock on tty-&amp;gt;ldisc_sem (via tty_ldisc_ref()).
Because slip_hangup() simply called slip_close(), it ran concurrently
with reader functions such as slip_receive_buf().&lt;/p&gt;
&lt;p&gt;slip_close() unregisters and frees the net device and its private
struct slip, causing concurrent reader threads in slip_receive_buf()
to dereference freed memory.&lt;/p&gt;
&lt;p&gt;Line discipline close() is already guaranteed to be called under
the write lock of tty-&amp;gt;ldisc_sem during hangup processing
(in tty_ldisc_reinit() or tty_ldisc_kill()).&lt;/p&gt;
&lt;p&gt;Remove slip_hangup() so teardown is serialized cleanly by slip_close().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;slip: remove slip_hangup() to fix use-after-free in slip_receive_buf()&lt;/p&gt;
&lt;p&gt;Jaeyoung Chung and Eulgyu Kim reported a slab-use-after-free read
in slip_receive_buf() when racing against tty hangup.&lt;/p&gt;
&lt;p&gt;tty_ldisc_hangup() calls ld-&amp;gt;ops-&amp;gt;hangup() while holding only
a read lock on tty-&amp;gt;ldisc_sem (via tty_ldisc_ref()).
Because slip_hangup() simply called slip_close(), it ran concurrently
with reader functions such as slip_receive_buf().&lt;/p&gt;
&lt;p&gt;slip_close() unregisters and frees the net device and its private
struct slip, causing concurrent reader threads in slip_receive_buf()
to dereference freed memory.&lt;/p&gt;
&lt;p&gt;Line discipline close() is already guaranteed to be called under
the write lock of tty-&amp;gt;ldisc_sem during hangup processing
(in tty_ldisc_reinit() or tty_ldisc_kill()).&lt;/p&gt;
&lt;p&gt;Remove slip_hangup() so teardown is serialized cleanly by slip_close().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90057</guid>
    </item>
  </channel>
</rss>
