<?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>Wed, 30 Sep 2026 17:14:35 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-90057</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-90057</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-90057</guid>
    </item>
    <item>
      <title>fkie_cve-2026-90057</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-90057</link>
      <description>&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;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/fkie_cve-2026-90057</guid>
    </item>
    <item>
      <title>GHSA-45fm-hw2m-668x</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-45fm-hw2m-668x</link>
      <description>&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;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/ghsa-45fm-hw2m-668x</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-90057</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90057</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() Jaeyoung Chung and Eulgyu Kim reported a slab-use-after-free read in slip_receive_buf() when racing against tty hangup. 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(). 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. 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()). 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; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() Jaeyoung Chung and Eulgyu Kim reported a slab-use-after-free read in slip_receive_buf() when racing against tty hangup. 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(). 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. 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()). Remove slip_hangup() so teardown is serialized cleanly by slip_close().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-90057</guid>
    </item>
  </channel>
</rss>
