<?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:02:55.142861+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/alsa-2026:18587</id>
    <title>ALSA-2026:18587 — Moderate: kernel security update</title>
    <updated>2026-11-21T02:02:55.160832+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 more</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: bonding: check xdp prog when set bond mode (CVE-2025-22105)
  * kernel: block: fix resource leak in blk_register_queue() error path (CVE-2025-37980)
  * kernel: dmaengine: idxd: fix memory leak in error handling path of idxd_alloc (CVE-2025-38015)
  * kernel: espintcp: remove encap socket caching to avoid reference leak (CVE-2025-38097)
  * kernel: bpf: fix ktls panic with sockmap (CVE-2025-38166)
  * kernel: bpf: Do not include stack ptr register in precision backtracking bookkeeping (CVE-2025-38279)
  * kernel: nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails (CVE-2025-38400)
  * kernel: nvmet: fix memory leak of bio integrity (CVE-2025-38405)
  * kernel: netfilter: flowtable: account for Ethernet header in nf_flow_pppoe_proto() (CVE-2025-38441)
  * kernel: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime (CVE-2025-38470)
  * kernel: fs: writeback: fix use-after-free in __mark_inode_dirty() (CVE-2025-39866)
  * kernel: dm: fix NULL pointer dereference in __dm_suspend() (CVE-2025-40134)
  * kernel: wifi: mac80211_hwsim: fix typo in frequency notification (CVE-2026-23040)
  * kernel: Linux kernel: Denial of service and memory corruption in RDMA umad (CVE-2026-23243)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the C…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:18587"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2025-38400</id>
    <title>BELL-CVE-2025-38400</title>
    <updated>2026-11-21T02:02:55.160983+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-2025-38400"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</id>
    <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
    <updated>2026-11-21T02:02:55.161006+00:00</updated>
    <content>certfr-2025-avi-0698</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0698"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1959</id>
    <title>OESA-2025-1959 — kernel security update</title>
    <updated>2026-11-21T02:02:55.161020+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>xfrm: state: fix out-of-bounds read during lookup</p>
<p>lookup and resize can run in parallel.</p>
<p>The xfrm_state_hash_generation seqlock ensures a retry, but the hash
functions can observe a hmask value that is too large for the new hlist
array.</p>
<p>rehash does:
  rcu_assign_pointer(net-&amp;gt;xfrm.state_bydst, ndst) [..]
  net-&amp;gt;xfrm.state_hmask = nhashmask;</p>
<p>While state lookup does:
  h = xfrm_dst_hash(net, daddr, saddr, tmpl-&amp;gt;reqid, encap_family);
  hlist_for_each_entry_rcu(x, net-&amp;gt;xfrm.state_bydst + h, bydst) {</p>
<p>This is only safe in case the update to state_bydst is larger than
net-&amp;gt;xfrm.xfrm_state_hmask (or if the lookup function gets
serialized via state spinlock again).</p>
<p>Fix this by prefetching state_hmask and the associated pointers.
The xfrm_state_hash_generation seqlock retry will ensure that the pointer
and the hmask will be consistent.</p>
<p>The existing helpers, like xfrm_dst_hash(), are now unsafe for RCU side,
add lockdep assertions to document that they are only safe for insert
side.</p>
<p>xfrm_state_lookup_byaddr() uses the spinlock rather than RCU.
AFAICS this is an oversight from back when state lookup was converted to
RCU, this lock should be replaced with RCU in a future patch.(CVE-2024-57982)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>eth: bnxt: always recalculate features after XDP clearing, fix n…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1959"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38400</id>
    <title>UBUNTU-CVE-2025-38400</title>
    <updated>2026-11-21T02:02:55.161348+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 178 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails. syzbot reported a warning below [1] following a fault injection in nfs_fs_proc_net_init(). [0] When nfs_fs_proc_net_init() fails, /proc/net/rpc/nfs is not removed. Later, rpc_proc_exit() tries to remove /proc/net/rpc, and the warning is logged as the directory is not empty. Let's handle the error of nfs_fs_proc_net_init() properly. [0]: FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 CPU: 1 UID: 0 PID: 6120 Comm: syz.2.27 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace:  &lt;TASK&gt;   dump_stack_lvl (lib/dump_stack.c:123)  should_fail_ex (lib/fault-inject.c:73 lib/fault-inject.c:174)  should_failslab (mm/failslab.c:46)  kmem_cache_alloc_noprof (mm/slub.c:4178 mm/slub.c:4204)  __proc_create (fs/proc/generic.c:427)  proc_create_reg (fs/proc/generic.c:554)  proc_create_net_data (fs/proc/proc_net.c:120)  nfs_fs_proc_net_init (fs/nfs/client.c:1409)  nfs_net_init (fs/nfs/inode.c:2600)  ops_init (net/core/net_namespace.c:138)  setup_net (net/core/net_namespace.c:443)  copy_net_ns (net/core/net_namespace.c:576)  create_new_namespaces (kernel/nsproxy.c:110)  unshare_nsproxy_namespaces (kernel/nsproxy.c:218 (discriminator 4))  ksys_unshare (kernel/fork.c:3123)  __x64_sys_unshare (kernel/for…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38400"/>
  </entry>
</feed>
