<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 07:59:30 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98840</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-98840</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://127.0.0.1:10001/vuln/bell-cve-2026-98840</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1375</link>
      <description>certfr-2026-avi-1375</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1375</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98840</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98840</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 173 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vc_screen: reload vc pointer before if (ret) in vcs_write() to avoid UAF The reload of &amp;#39;vc&amp;#39; added by commit 8fb9ea65c9d1 (&amp;#34;vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF&amp;#34;) sits after the &amp;#39;if (ret)&amp;#39; block, so the copy-failure break path exits the loop without reloading vc. If the vc was kfree()&amp;#39;d via vc_port_destruct during the unlocked copy_from_user() window, the post-loop &amp;#39;if (written &amp;amp;&amp;amp; vc) vcs_scr_updated(vc)&amp;#39; is reached with a stale non-NULL vc. The &amp;#39;&amp;amp;&amp;amp; vc&amp;#39; guard from commit a287620312dc (&amp;#34;vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write&amp;#34;) only handles the NULL case, not this stale-non-NULL case; vcs_notifier() then reads param-&amp;gt;vc-&amp;gt;vc_num from freed memory:   BUG: KASAN: slab-use-after-free in vcs_notifier+0x7c/0xd0   Read of size 2 at addr ffff888007149190   Call Trace:    vcs_notifier+0x7c/0xd0    atomic_notifier_call_chain+0x70/0xa0    vcs_scr_updated+0x77/0xa0    vcs_write+0x71b/0x7e0   Allocated by task: vc_allocate -&amp;gt; con_install -&amp;gt; tty_open   Freed by task: kfree &amp;lt;- vt_ioctl (VT_DISALLOCATE -&amp;gt; vc_port_destruct) Move the reload to immediately after console_lock(), before &amp;#39;if (ret)&amp;#39;, so every break path below passes a fresh vc to the post-loop vcs_scr_updated().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 173 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vc_screen: reload vc pointer before if (ret) in vcs_write() to avoid UAF The reload of &amp;#39;vc&amp;#39; added by commit 8fb9ea65c9d1 (&amp;#34;vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF&amp;#34;) sits after the &amp;#39;if (ret)&amp;#39; block, so the copy-failure break path exits the loop without reloading vc. If the vc was kfree()&amp;#39;d via vc_port_destruct during the unlocked copy_from_user() window, the post-loop &amp;#39;if (written &amp;amp;&amp;amp; vc) vcs_scr_updated(vc)&amp;#39; is reached with a stale non-NULL vc. The &amp;#39;&amp;amp;&amp;amp; vc&amp;#39; guard from commit a287620312dc (&amp;#34;vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write&amp;#34;) only handles the NULL case, not this stale-non-NULL case; vcs_notifier() then reads param-&amp;gt;vc-&amp;gt;vc_num from freed memory:   BUG: KASAN: slab-use-after-free in vcs_notifier+0x7c/0xd0   Read of size 2 at addr ffff888007149190   Call Trace:    vcs_notifier+0x7c/0xd0    atomic_notifier_call_chain+0x70/0xa0    vcs_scr_updated+0x77/0xa0    vcs_write+0x71b/0x7e0   Allocated by task: vc_allocate -&amp;gt; con_install -&amp;gt; tty_open   Freed by task: kfree &amp;lt;- vt_ioctl (VT_DISALLOCATE -&amp;gt; vc_port_destruct) Move the reload to immediately after console_lock(), before &amp;#39;if (ret)&amp;#39;, so every break path below passes a fresh vc to the post-loop vcs_scr_updated().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98840</guid>
    </item>
  </channel>
</rss>
