<?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 10:16:13 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-23371</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-23371</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-23371</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1473 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1473</link>
      <description>certfr-2026-avi-1473</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1473</guid>
    </item>
    <item>
      <title>OESA-2026-1862 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-1862</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to detect potential corrupted nid in free_nid_list&lt;/p&gt;
&lt;p&gt;As reported, on-disk footer.ino and footer.nid is the same and
out-of-range, let&amp;amp;apos;s add sanity check on f2fs_alloc_nid() to detect
any potential corruption in free_nid_list.(CVE-2025-68315)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntfs3: Fix uninit buffer allocated by __getname()&lt;/p&gt;
&lt;p&gt;Fix uninit errors caused after buffer allocation given to &amp;amp;apos;de&amp;amp;apos;; by
initializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nf_tables: fix use-after-free in nf_tables_addchain()&lt;/p&gt;
&lt;p&gt;nf_tables_addchain() publishes the chain to table-&amp;amp;gt;chains via
list_add_tail_rcu() (in nft_chain_add()) before registering hooks.
If nf_tables_register_hook() then fails, the error path calls
nft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy()
with no RCU grace period in between.&lt;/p&gt;
&lt;p&gt;This creates two use-after-free conditions:&lt;/p&gt;
&lt;p&gt;1) Control-plane: nf_tables_dump_chains() traverses table-&amp;amp;gt;chains
    under rcu_read_lock(). A concurrent dump can still be walking
    the chain when the error path frees it.&lt;/p&gt;
&lt;p&gt;2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly
    installs the IPv4 hook before IPv6 registration fails.  Packets
    entering nft…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to detect potential corrupted nid in free_nid_list&lt;/p&gt;
&lt;p&gt;As reported, on-disk footer.ino and footer.nid is the same and
out-of-range, let&amp;amp;apos;s add sanity check on f2fs_alloc_nid() to detect
any potential corruption in free_nid_list.(CVE-2025-68315)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntfs3: Fix uninit buffer allocated by __getname()&lt;/p&gt;
&lt;p&gt;Fix uninit errors caused after buffer allocation given to &amp;amp;apos;de&amp;amp;apos;; by
initializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nf_tables: fix use-after-free in nf_tables_addchain()&lt;/p&gt;
&lt;p&gt;nf_tables_addchain() publishes the chain to table-&amp;amp;gt;chains via
list_add_tail_rcu() (in nft_chain_add()) before registering hooks.
If nf_tables_register_hook() then fails, the error path calls
nft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy()
with no RCU grace period in between.&lt;/p&gt;
&lt;p&gt;This creates two use-after-free conditions:&lt;/p&gt;
&lt;p&gt;1) Control-plane: nf_tables_dump_chains() traverses table-&amp;amp;gt;chains
    under rcu_read_lock(). A concurrent dump can still be walking
    the chain when the error path frees it.&lt;/p&gt;
&lt;p&gt;2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly
    installs the IPv4 hook before IPv6 registration fails.  Packets
    entering nft…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-1862</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23371</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23371</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting Running stress-ng --schedpolicy 0 on an RT kernel on a big machine might lead to the following WARNINGs (edited).  sched: DL de-boosted task PID 22725: REPLENISH flag missing  WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8  ... (running_bw underflow)  Call trace:   dequeue_task_dl+0x15c/0x1f8 (P)   dequeue_task+0x80/0x168   deactivate_task+0x24/0x50   push_dl_task+0x264/0x2e0   dl_task_timer+0x1b0/0x228   __hrtimer_run_queues+0x188/0x378   hrtimer_interrupt+0xfc/0x260   ... The problem is that when a SCHED_DEADLINE task (lock holder) is changed to a lower priority class via sched_setscheduler(), it may fail to properly inherit the parameters of potential DEADLINE donors if it didn&amp;#39;t already inherit them in the past (shorter deadline than donor&amp;#39;s at that time). This might lead to bandwidth accounting corruption, as enqueue_task_dl() won&amp;#39;t recognize the lock holder as boosted. The scenario occurs when: 1. A DEADLINE task (donor) blocks on a PI mutex held by another    DEADLINE task (holder), but the holder doesn&amp;#39;t inherit parameters    (e.g., it already has a shorter deadline) 2. sched_setscheduler() changes the holder from DEADLINE to a lower    class while still holding the mutex 3. The holder should now inherit DEADLINE parameters from the donor    and be enqueued with ENQUEUE_REPLENISH, but this doesn&amp;#39;t…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 203 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting Running stress-ng --schedpolicy 0 on an RT kernel on a big machine might lead to the following WARNINGs (edited).  sched: DL de-boosted task PID 22725: REPLENISH flag missing  WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8  ... (running_bw underflow)  Call trace:   dequeue_task_dl+0x15c/0x1f8 (P)   dequeue_task+0x80/0x168   deactivate_task+0x24/0x50   push_dl_task+0x264/0x2e0   dl_task_timer+0x1b0/0x228   __hrtimer_run_queues+0x188/0x378   hrtimer_interrupt+0xfc/0x260   ... The problem is that when a SCHED_DEADLINE task (lock holder) is changed to a lower priority class via sched_setscheduler(), it may fail to properly inherit the parameters of potential DEADLINE donors if it didn&amp;#39;t already inherit them in the past (shorter deadline than donor&amp;#39;s at that time). This might lead to bandwidth accounting corruption, as enqueue_task_dl() won&amp;#39;t recognize the lock holder as boosted. The scenario occurs when: 1. A DEADLINE task (donor) blocks on a PI mutex held by another    DEADLINE task (holder), but the holder doesn&amp;#39;t inherit parameters    (e.g., it already has a shorter deadline) 2. sched_setscheduler() changes the holder from DEADLINE to a lower    class while still holding the mutex 3. The holder should now inherit DEADLINE parameters from the donor    and be enqueued with ENQUEUE_REPLENISH, but this doesn&amp;#39;t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23371</guid>
    </item>
  </channel>
</rss>
