<?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-21T00:23:07.675965+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-23025</id>
    <title>BELL-CVE-2026-23025</title>
    <updated>2026-11-21T00:23:07.692963+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-23025"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0166</id>
    <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
    <updated>2026-11-21T00:23:07.693048+00:00</updated>
    <content>certfr-2026-avi-0166</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0166"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-1566</id>
    <title>OESA-2026-1566 — kernel security update</title>
    <updated>2026-11-21T00:23:07.693070+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: 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>udp: Deal with race between UDP socket address change and rehash</p>
<p>If a UDP socket changes its local address while it&amp;apos;s receiving
datagrams, as a result of connect(), there is a period during which
a lookup operation might fail to find it, after the address is changed
but before the secondary hash (port and address) and the four-tuple
hash (local and remote ports and addresses) are updated.</p>
<p>Secondary hash chains were introduced by commit 30fff9231fad (&amp;quot;udp:
bind() optimisation&amp;quot;) and, as a result, a rehash operation became
needed to make a bound socket reachable again after a connect().</p>
<p>This operation was introduced by commit 719f835853a9 (&amp;quot;udp: add
rehash on connect()&amp;quot;) which isn&amp;apos;t however a complete fix: the
socket will be found once the rehashing completes, but not while
it&amp;apos;s pending.</p>
<p>This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a
client sending datagrams to it. After the server receives the first
datagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to
the address of the sender, in order to set up a directed flow.</p>
<p>Now, if the client, running on a different CPU thread, happens to
send a (subsequent) datagram while the server&amp;apos;s socket changes its
address, but is not rehashed yet, this will result in a failed
lookup and a port unreachable error delivered to the…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-1566"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23025</id>
    <title>UBUNTU-CVE-2026-23025</title>
    <updated>2026-11-21T00:23:07.693527+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: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 140 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: mm/page_alloc: prevent pcp corruption with SMP=n The kernel test robot has reported:  BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28   lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0  CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT 8cc09ef94dcec767faa911515ce9e609c45db470  Call Trace:   &lt;IRQ&gt;   __dump_stack (lib/dump_stack.c:95)   dump_stack_lvl (lib/dump_stack.c:123)   dump_stack (lib/dump_stack.c:130)   spin_dump (kernel/locking/spinlock_debug.c:71)   do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)   _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)   __free_frozen_pages (mm/page_alloc.c:2973)   ___free_pages (mm/page_alloc.c:5295)   __free_pages (mm/page_alloc.c:5334)   tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)   ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)   ? rcu_core (kernel/rcu/tree.c:?)   rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)   rcu_core_si (kernel/rcu/tree.c:2879)   handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)   __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)   irq_exit_rcu (kernel/softirq.c:741)   sysvec_apic_timer_interrupt (arch/x…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23025"/>
  </entry>
</feed>
