<?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:22:49.128995+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:61887</id>
    <title>ALSA-2026:61887 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T00:22:49.142360+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: seccomp: passthrough uretprobe systemcall without filtering (CVE-2025-21834)
  * kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)
  * kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks (CVE-2026-43454)
  * kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (CVE-2026-43450)
  * kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)
  * kernel: ip6_gre: Use cached t-&gt;net in ip6erspan_changelink() (CVE-2026-46120)
  * kernel: iommu/amd: Fix clone_alias() to use the original device's devid (CVE-2026-53053)
  * kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg (CVE-2026-53026)
  * kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)
  * kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() (CVE-2026-53196)
  * kernel: mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189)
  * kernel: mm/list_lru: drain before clearing xarray entry on reparent (CVE-2026-53153)
  * kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)
  * kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)
  * kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)
  * kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:61887"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-53399</id>
    <title>BELL-CVE-2026-53399</title>
    <updated>2026-11-21T00:22:49.142415+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-53399"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0930</id>
    <title>certfr-2026-avi-0930 — 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:22:49.142441+00:00</updated>
    <content>certfr-2026-avi-0930</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0930"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-3316</id>
    <title>OESA-2026-3316 — kernel security update</title>
    <updated>2026-11-21T00:22:49.142451+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP4: 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>NFSv4/flexfiles: reject zero filehandle version count</p>
<p>ff_layout_alloc_lseg() decodes the filehandle-version array count
from the flexfiles layout body. The value is used as the count for
kzalloc_objs(), and the current code only rejects NULL.</p>
<p>A zero count yields ZERO_SIZE_PTR, which can be stored in
dss_info-&amp;gt;fh_versions even though later flexfiles paths assume that at
least one filehandle version exists.</p>
<p>Reject fh_count == 0 before the allocation, matching the existing zero
version_count validation in the flexfiles GETDEVICEINFO parser.</p>
<p>A QEMU/KASAN run with a malformed flexfiles layout hit:</p>
<p>KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
  RIP: 0010:ff_layout_encode_ff_layoutupdate.isra.0+0x15f/0x750
  ff_layout_encode_layoutreturn+0x683/0x970
  nfs4_xdr_enc_layoutreturn+0x278/0x3a0
  Kernel panic - not syncing: Fatal exception</p>
<p>The patched kernel rejects the malformed layout without KASAN/oops/panic,
and a valid fh_count=1 regression still opens, reads, and unmounts cleanly.(CVE-2026-53392)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>nfsd: release layout stid on setlease failure</p>
<p>nfs4_alloc_stid() publishes the new stid into cl-&amp;gt;cl_stateids via
idr_alloc_cyclic() under cl_lock before returning to
nfsd4_alloc_layout_stateid(). When nfsd4_layout_setlease() then
fails, the…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-3316"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:61887</id>
    <title>RLSA-2026:61887 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T00:22:49.142504+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: rtla, Rocky Linux:10: kernel-modules-core, Rocky Linux:10: kernel-debug-devel, Rocky Linux:10: kernel-debug, Rocky Linux:10: rv, Rocky Linux:10: perf-debuginfo, Rocky Linux:10: kernel, Rocky Linux:10: kernel-debuginfo-common-ppc64le, Rocky Linux:10: kernel-debuginfo, Rocky Linux:10: python3-perf and 78 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: seccomp: passthrough uretprobe systemcall without filtering (CVE-2025-21834)</p>
<p>* kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)</p>
<p>* kernel: netfilter: nf_tables: Fix for duplicate device in netdev hooks (CVE-2026-43454)</p>
<p>* kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() (CVE-2026-43450)</p>
<p>* kernel: bonding: alb: fix UAF in rlb_arp_recv during bond up/down (CVE-2026-45970)</p>
<p>* kernel: ip6_gre: Use cached t-&gt;net in ip6erspan_changelink() (CVE-2026-46120)</p>
<p>* kernel: iommu/amd: Fix clone_alias() to use the original device's devid (CVE-2026-53053)</p>
<p>* kernel: NFSD: fix nfs4_file access extra count in nfsd4_add_rdaccess_to_wrdeleg (CVE-2026-53026)</p>
<p>* kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)</p>
<p>* kernel: USB: serial: io_ti: fix heap overflow in get_manuf_info() (CVE-2026-53196)</p>
<p>* kernel: mm/huge_memory: update file PMD counter before folio_put() (CVE-2026-53189)</p>
<p>* kernel: mm/list_lru: drain before clearing xarray entry on reparent (CVE-2026-53153)</p>
<p>* kernel: pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)</p>
<p>* kernel: nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)</p>
<p>* kernel: nfsd: release layout stid on setlease failure (CVE-2026-53399)</p>
<p>* kernel: NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)</p>
<p>* kernel: NF…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rlsa-2026:61887"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53399</id>
    <title>UBUNTU-CVE-2026-53399</title>
    <updated>2026-11-21T00:22:49.142595+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: nfsd: release layout stid on setlease failure nfs4_alloc_stid() publishes the new stid into cl-&gt;cl_stateids via idr_alloc_cyclic() under cl_lock before returning to nfsd4_alloc_layout_stateid(). When nfsd4_layout_setlease() then fails, the error path frees the layout stateid directly with kmem_cache_free() without ever calling idr_remove(), leaving the IDR slot pointing at freed slab memory. Any subsequent IDR walker (states_show, client teardown) dereferences the dangling pointer. The correct teardown for an IDR-published stid is nfs4_put_stid(), which removes the IDR slot under cl_lock, dispatches sc_free (nfsd4_free_layout_stateid) to release ls-&gt;ls_file via nfsd4_close_layout(), and drops the nfs4_file reference in its tail. A second issue blocks that switch: nfsd4_free_layout_stateid() unconditionally inspects ls-&gt;ls_fence_work via delayed_work_pending() under ls_lock, but INIT_DELAYED_WORK(&amp;ls-&gt;ls_fence_work, ...) currently runs only after the setlease call. On the setlease-failure path the destructor would touch an uninitialized delayed_work.     nfsd4_alloc_layout_stateid()       nfs4_alloc_stid()           /* idr_alloc_cyclic under cl_lock */       nfsd4_layout_setlease()     /* fails */         nfs4_put_stid()           nfsd4_free_layout_stateid()             delayed_work_pending(&amp;ls-&gt;ls_fence_work)  /* needs INIT */             nfsd4_close_layout()  /* nfsd_file_put(ls-&gt;ls_file) */           put_n…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53399"/>
  </entry>
</feed>
