<?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:25:19.857314+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-23300</id>
    <title>BELL-CVE-2026-23300</title>
    <updated>2026-11-21T02:25:19.876709+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-23300"/>
  </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:25:19.876794+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:25:19.876817+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-23300</id>
    <title>UBUNTU-CVE-2026-23300</title>
    <updated>2026-11-21T02:25:19.877107+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: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop When a standalone IPv6 nexthop object is created with a loopback device (e.g., "ip -6 nexthop add id 100 dev lo"), fib6_nh_init() misclassifies it as a reject route. This is because nexthop objects have no destination prefix (fc_dst=::), causing fib6_is_reject() to match any loopback nexthop. The reject path skips fib_nh_common_init(), leaving nhc_pcpu_rth_output unallocated. If an IPv4 route later references this nexthop, __mkroute_output() dereferences NULL nhc_pcpu_rth_output and panics. Simplify the check in fib6_nh_init() to only match explicit reject routes (RTF_REJECT) instead of using fib6_is_reject(). The loopback promotion heuristic in fib6_is_reject() is handled separately by ip6_route_info_create_nh(). After this change, the three cases behave as follows: 1. Explicit reject route ("ip -6 route add unreachable 2001:db8::/64"):    RTF_REJECT is set, enters reject path, skips fib_nh_common_init().    No behavior change. 2. Implicit loopback reject route ("ip -6 route add 2001:db8::/32 dev lo"):    RTF_REJECT is not set, takes normal path, fib_nh_common_init() is    called. ip6_route_info_create_nh() still promotes it to reject    afterward. nhc_pcpu_rth_output is allocated but unused, which is    harmless. 3. Standalone nexthop object ("ip -6 nexthop add id 100 dev lo"):    RTF_REJECT is not set, takes normal path, fib_nh_common_i…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23300"/>
  </entry>
</feed>
