<?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-21T15:51:15.157576+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:77690</id>
    <title>ALSA-2026:77690 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T15:51:15.173716+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: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)
  * kernel: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use (CVE-2026-53360)
  * kernel: vsock/virtio: fix zerocopy completion for multi-skb sends (CVE-2026-53365)
  * kernel: NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)
  * kernel: vsock/virtio: bind uarg before filling zerocopy skb (CVE-2026-63970)
  * kernel: igc: set tx buffer type for SMD frames (CVE-2026-64035)
  * kernel: vsock/vmci: fix UAF when peer resets connection during handshake (CVE-2026-64115)
  * kernel: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (CVE-2026-72317)
  * kernel: udp: fix potential use-after-free in tunnel segmentation (CVE-2026-74705)
  * kernel: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (CVE-2026-74744)
  * kernel: nfsd: defer vfree of compound ops to fix rpc_status UAF (CVE-2026-89690)
  * kernel: nfsd: initialize copy-notify stateid before publishing it (CVE-2026-89669)
  * kernel: svcrdma: Reject inline replies that overflow the pull-up buffer (CVE-2026-89530)
  * kernel: nfsd: fix stale s2s_cp_stateids IDR entry for async COPY (CVE-2026-89676)
  * kernel: nfsd: revoke copy-notify stateids before dropping their reference (CVE-2026-89663)
  * kernel: nfsd: fix UAF in async copy cancel and shutdown (CVE-2026-89675)</p>
<p>Bug Fix(es) and Enhancement(s):…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:77690"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-89676</id>
    <title>BELL-CVE-2026-89676</title>
    <updated>2026-11-21T15:51:15.173828+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-89676"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</id>
    <title>certfr-2026-avi-1253 — 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-21T15:51:15.173853+00:00</updated>
    <content>certfr-2026-avi-1253</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1253"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-4357</id>
    <title>OESA-2026-4357 — kernel security update</title>
    <updated>2026-11-21T15:51:15.173869+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.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>fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist</p>
<p>Index allocation requires at least one bit in the $BITMAP attribute to
track usage of index entries. If the bitmap is empty while index blocks
are already present, this reflects on-disk corruption.</p>
<p>syzbot triggered this condition using a malformed NTFS image. During a
rename() operation involving a long filename (which spans multiple
index entries), the empty bitmap allowed the name to be added without
valid tracking. Subsequent deletion of the original entry failed with
-ENOENT, due to unexpected index state.</p>
<p>Reject such cases by verifying that the bitmap is not empty when index
blocks exist.(CVE-2025-40067)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>batman-adv: fix fragment reassembly length accounting</p>
<p>batman-adv keeps a running payload length for queued fragments and uses it
to validate a fragment chain before reassembly.</p>
<p>That accounting currently allows the accumulated fragment length to be
truncated during updates. As a result, malformed fragment chains can
bypass the intended validation and drive reassembly with inconsistent
length state, leading to a local denial of service.</p>
<p>Fix the accounting by storing the accumulated length in a length-typed
field and rejecting update overflows before the existing validation logic
runs.</p>
<p>T…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-4357"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:77690</id>
    <title>RLSA-2026:77690 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T15:51:15.174224+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: rv, Rocky Linux:10: kernel-core, Rocky Linux:10: kernel-modules-extra-matched, Rocky Linux:10: kernel-zfcpdump-debuginfo, Rocky Linux:10: kernel-devel, Rocky Linux:10: kernel-modules-extra, Rocky Linux:10: kernel-zfcpdump-modules-core, Rocky Linux:10: kernel-debuginfo-common-s390x, Rocky Linux:10: python3-perf-debuginfo, Rocky Linux:10: perf-debuginfo and 80 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: ipvlan: Make the addrs_lock be per port (CVE-2026-23103)</p>
<p>* kernel: KVM: SEV: Require in-GHCB scratch area if GHCB v2+ is in use (CVE-2026-53360)</p>
<p>* kernel: vsock/virtio: fix zerocopy completion for multi-skb sends (CVE-2026-53365)</p>
<p>* kernel: NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)</p>
<p>* kernel: vsock/virtio: bind uarg before filling zerocopy skb (CVE-2026-63970)</p>
<p>* kernel: igc: set tx buffer type for SMD frames (CVE-2026-64035)</p>
<p>* kernel: vsock/vmci: fix UAF when peer resets connection during handshake (CVE-2026-64115)</p>
<p>* kernel: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (CVE-2026-72317)</p>
<p>* kernel: udp: fix potential use-after-free in tunnel segmentation (CVE-2026-74705)</p>
<p>* kernel: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (CVE-2026-74744)</p>
<p>* kernel: nfsd: defer vfree of compound ops to fix rpc_status UAF (CVE-2026-89690)</p>
<p>* kernel: nfsd: initialize copy-notify stateid before publishing it (CVE-2026-89669)</p>
<p>* kernel: svcrdma: Reject inline replies that overflow the pull-up buffer (CVE-2026-89530)</p>
<p>* kernel: nfsd: fix stale s2s_cp_stateids IDR entry for async COPY (CVE-2026-89676)</p>
<p>* kernel: nfsd: revoke copy-notify stateids before dropping their reference (CVE-2026-89663)</p>
<p>* kernel: nfsd: fix UAF in async copy cancel and shutdown (CVE-2026-89675)</p>
<p>Bug Fix(es) and Enhancement(s):</p>
<p>* mlxbf_bootctl: drive…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rlsa-2026:77690"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89676</id>
    <title>UBUNTU-CVE-2026-89676</title>
    <updated>2026-11-21T15:51:15.174394+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 220 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: nfsd: fix stale s2s_cp_stateids IDR entry for async COPY For an async COPY, nfsd4_copy() called nfs4_init_copy_state() before dup_copy_fields(), so the s2s_cp_stateids IDR was pointed at &amp;u-&gt;copy-&gt;cp_stateid -- memory in the per-rqstp COMPOUND buffer that is reused by the next request. dup_copy_fields() copies only the value into async_copy, so the IDR slot dangled at the transient buffer for the whole background copy. Any IDR walker then dereferences reused request memory: the laundromat reads cs_type from it and, if the bytes look like an expired NFS4_COPYNOTIFY_STID, follows into refcount_dec()/idr_remove()/kfree() on garbage; manage_cpntf_state() has the same exposure via idr_find(). Duplicate the fields first, then register the stateid on the stable async_copy. result-&gt;cb_stateid is unchanged.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89676"/>
  </entry>
</feed>
