<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T02:47:21.432768+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-23368</id>
    <title>BELL-CVE-2026-23368</title>
    <updated>2026-11-21T02:47:21.450087+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-23368"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0376</id>
    <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>
    <updated>2026-11-21T02:47:21.450159+00:00</updated>
    <content>certfr-2026-avi-0376</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0376"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-1862</id>
    <title>OESA-2026-1862 — kernel security update</title>
    <updated>2026-11-21T02:47:21.450180+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>f2fs: fix to detect potential corrupted nid in free_nid_list</p>
<p>As reported, on-disk footer.ino and footer.nid is the same and
out-of-range, let&amp;apos;s add sanity check on f2fs_alloc_nid() to detect
any potential corruption in free_nid_list.(CVE-2025-68315)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ntfs3: Fix uninit buffer allocated by __getname()</p>
<p>Fix uninit errors caused after buffer allocation given to &amp;apos;de&amp;apos;; by
initializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: nf_tables: fix use-after-free in nf_tables_addchain()</p>
<p>nf_tables_addchain() publishes the chain to table-&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.</p>
<p>This creates two use-after-free conditions:</p>
<p>1) Control-plane: nf_tables_dump_chains() traverses table-&amp;gt;chains
    under rcu_read_lock(). A concurrent dump can still be walking
    the chain when the error path frees it.</p>
<p>2) Packet path: for NFPROTO_INET, nf_register_net_hook() briefly
    installs the IPv4 hook before IPv6 registration fails.  Packets
    entering nft…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-1862"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23368</id>
    <title>UBUNTU-CVE-2026-23368</title>
    <updated>2026-11-21T02:47:21.450471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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] [&lt;8054e4b8&gt;] led_trigger_register+0x5c/0x1fc             &lt;-- Trying to get lock "triggers_list_lock" via down_write(&amp;triggers_list_lock); [ 1362.054536] [&lt;80662830&gt;] phy_led_triggers_register+0xd0/0x234 [ 1362.060329] [&lt;8065e200&gt;] phy_attach_direct+0x33c/0x40c [ 1362.065489] [&lt;80651fc4&gt;] phylink_fwnode_phy_connect+0x15c/0x23c [ 1362.071480] [&lt;8066ee18&gt;] mtk_open+0x7c/0xba0 [ 1362.075849] [&lt;806d714c&gt;] __dev_open+0x280/0x2b0 [ 1362.080384] [&lt;806d7668&gt;] __dev_change_flags+0x244/0x24c [ 1362.085598] [&lt;806d7698&gt;] dev_change_flags+0x28/0x78 [ 1362.090528] [&lt;807150e4&gt;] dev_ioctl+0x4c0/0x654                       &lt;-- Hold lock "rtnl_mutex" by calling rtnl_lock(); [ 1362.094985] [&lt;80694360&gt;] sock_ioctl+0x2f4/0x4e0 [ 1362.099567] [&lt;802e9c4c&gt;] sys_ioctl+0x32c/0xd8c [ 1362.104022] [&lt;80014504&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] [&lt;806c2640&gt;] register_netdevice_notifier+0x60/0x168      &lt;-- Trying to get lock "rtnl_mutex" via rtnl_lock(); [ 1362.197073] [&lt;805504ac&gt;] netdev_trig_activate+0x194/0x1e4 [ 1362.202490] [&lt;8054e28c&gt;] led_trigger_set+0x1d4/0x360                 &lt;-- Hold lock "triggers_list_lock" by down_read(&amp;trigge…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23368"/>
  </entry>
</feed>
