<?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 02:46:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-23368</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-23368</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-23368</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0376 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0376</link>
      <description>certfr-2026-avi-0376</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0376</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-23368</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23368</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 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock There is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and LED_TRIGGER_PHY are enabled: [ 1362.049207] [&amp;lt;8054e4b8&amp;gt;] led_trigger_register+0x5c/0x1fc             &amp;lt;-- Trying to get lock &amp;#34;triggers_list_lock&amp;#34; via down_write(&amp;amp;triggers_list_lock); [ 1362.054536] [&amp;lt;80662830&amp;gt;] phy_led_triggers_register+0xd0/0x234 [ 1362.060329] [&amp;lt;8065e200&amp;gt;] phy_attach_direct+0x33c/0x40c [ 1362.065489] [&amp;lt;80651fc4&amp;gt;] phylink_fwnode_phy_connect+0x15c/0x23c [ 1362.071480] [&amp;lt;8066ee18&amp;gt;] mtk_open+0x7c/0xba0 [ 1362.075849] [&amp;lt;806d714c&amp;gt;] __dev_open+0x280/0x2b0 [ 1362.080384] [&amp;lt;806d7668&amp;gt;] __dev_change_flags+0x244/0x24c [ 1362.085598] [&amp;lt;806d7698&amp;gt;] dev_change_flags+0x28/0x78 [ 1362.090528] [&amp;lt;807150e4&amp;gt;] dev_ioctl+0x4c0/0x654                       &amp;lt;-- Hold lock &amp;#34;rtnl_mutex&amp;#34; by calling rtnl_lock(); [ 1362.094985] [&amp;lt;80694360&amp;gt;] sock_ioctl+0x2f4/0x4e0 [ 1362.099567] [&amp;lt;802e9c4c&amp;gt;] sys_ioctl+0x32c/0xd8c [ 1362.104022] [&amp;lt;80014504&amp;gt;] syscall_common+0x34/0x58 Here LED_TRIGGER_PHY is registering LED triggers during phy_attach while holding RTNL and then taking triggers_list_lock. [ 1362.191101] [&amp;lt;806c2640&amp;gt;] register_netdevice_notifier+0x60/0x168      &amp;lt;-- Trying to get lock &amp;#34;rtnl_mutex&amp;#34; via rtnl_lock(); [ 1362.197073] [&amp;lt;805504ac&amp;gt;] netdev_trig_activate+0x194/0x1e4 [ 1362.202490] [&amp;lt;8054e28c&amp;gt;] led_trigger_set+0x1d4/0x360                 &amp;lt;-- Hold lock &amp;#34;triggers_list_lock&amp;#34; by down_read(&amp;amp;trigge…&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 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: phy: register phy led_triggers during probe to avoid AB-BA deadlock There is an AB-BA deadlock when both LEDS_TRIGGER_NETDEV and LED_TRIGGER_PHY are enabled: [ 1362.049207] [&amp;lt;8054e4b8&amp;gt;] led_trigger_register+0x5c/0x1fc             &amp;lt;-- Trying to get lock &amp;#34;triggers_list_lock&amp;#34; via down_write(&amp;amp;triggers_list_lock); [ 1362.054536] [&amp;lt;80662830&amp;gt;] phy_led_triggers_register+0xd0/0x234 [ 1362.060329] [&amp;lt;8065e200&amp;gt;] phy_attach_direct+0x33c/0x40c [ 1362.065489] [&amp;lt;80651fc4&amp;gt;] phylink_fwnode_phy_connect+0x15c/0x23c [ 1362.071480] [&amp;lt;8066ee18&amp;gt;] mtk_open+0x7c/0xba0 [ 1362.075849] [&amp;lt;806d714c&amp;gt;] __dev_open+0x280/0x2b0 [ 1362.080384] [&amp;lt;806d7668&amp;gt;] __dev_change_flags+0x244/0x24c [ 1362.085598] [&amp;lt;806d7698&amp;gt;] dev_change_flags+0x28/0x78 [ 1362.090528] [&amp;lt;807150e4&amp;gt;] dev_ioctl+0x4c0/0x654                       &amp;lt;-- Hold lock &amp;#34;rtnl_mutex&amp;#34; by calling rtnl_lock(); [ 1362.094985] [&amp;lt;80694360&amp;gt;] sock_ioctl+0x2f4/0x4e0 [ 1362.099567] [&amp;lt;802e9c4c&amp;gt;] sys_ioctl+0x32c/0xd8c [ 1362.104022] [&amp;lt;80014504&amp;gt;] syscall_common+0x34/0x58 Here LED_TRIGGER_PHY is registering LED triggers during phy_attach while holding RTNL and then taking triggers_list_lock. [ 1362.191101] [&amp;lt;806c2640&amp;gt;] register_netdevice_notifier+0x60/0x168      &amp;lt;-- Trying to get lock &amp;#34;rtnl_mutex&amp;#34; via rtnl_lock(); [ 1362.197073] [&amp;lt;805504ac&amp;gt;] netdev_trig_activate+0x194/0x1e4 [ 1362.202490] [&amp;lt;8054e28c&amp;gt;] led_trigger_set+0x1d4/0x360                 &amp;lt;-- Hold lock &amp;#34;triggers_list_lock&amp;#34; by down_read(&amp;amp;trigge…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23368</guid>
    </item>
  </channel>
</rss>
