<?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-21T14:45:02.638654+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:71329</id>
    <title>ALSA-2026:71329 — Important: kernel security update</title>
    <updated>2026-11-21T14:45:02.647067+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 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: drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (CVE-2026-31566)
  * kernel: netfilter: nf_queue: hold bridge skb-&gt;dev while queued (CVE-2026-52912)
  * kernel: Linux kernel: PPPoE memory corruption via stale pointer (CVE-2026-68121)
  * kernel: Linux kernel IPVS: Denial of Service due to stale memory references (CVE-2026-80714)
  * kernel: nvme-tcp: reject a read that transferred too few bytes (CVE-2026-89480)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:71329"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-89480</id>
    <title>BELL-CVE-2026-89480</title>
    <updated>2026-11-21T14:45:02.647121+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-89480"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1230</id>
    <title>certfr-2026-avi-1230 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un…</title>
    <updated>2026-11-21T14:45:02.647133+00:00</updated>
    <content>certfr-2026-avi-1230</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1230"/>
  </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-21T14:45:02.647141+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:71329</id>
    <title>RLSA-2026:71329 — Important: kernel security update</title>
    <updated>2026-11-21T14:45:02.647333+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:8: bpftool, Rocky Linux:8: bpftool-debuginfo, Rocky Linux:8: kernel, Rocky Linux:8: kernel-core, Rocky Linux:8: kernel-debug, Rocky Linux:8: kernel-debug-core, Rocky Linux:8: kernel-debug-debuginfo, Rocky Linux:8: kernel-debug-devel, Rocky Linux:8: kernel-debuginfo, Rocky Linux:8: kernel-debuginfo-common-aarch64 and 16 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: drm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib (CVE-2026-31566)</p>
<p>* kernel: netfilter: nf_queue: hold bridge skb-&gt;dev while queued (CVE-2026-52912)</p>
<p>* kernel: Linux kernel: PPPoE memory corruption via stale pointer (CVE-2026-68121)</p>
<p>* kernel: Linux kernel IPVS: Denial of Service due to stale memory references (CVE-2026-80714)</p>
<p>* kernel: nvme-tcp: reject a read that transferred too few bytes (CVE-2026-89480)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rlsa-2026:71329"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89480</id>
    <title>UBUNTU-CVE-2026-89480</title>
    <updated>2026-11-21T14:45:02.647362+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: nvme-tcp: reject a read that transferred too few bytes nvme_tcp_recv_data() completes a request once the current C2HData PDU has been consumed. Nothing compares the total bytes received against the length the command asked for: struct nvme_tcp_request has no receive-side counter, queue-&gt;data_remaining is per queue, and blk_mq_end_request() completes for blk_rq_bytes(rq) unconditionally with no residual concept anywhere above. A controller can therefore answer a 4096-byte read with 512 bytes and have it reported as a complete read; user space then gets 4096 bytes of which 3584 are whatever was already in the page. I reproduced that with a test target. Count the bytes received and refuse to complete a successful read whose count does not match, at the two NVME_TCP_F_DATA_SUCCESS paths and in nvme_tcp_process_nvme_cqe(). The success test shifts req-&gt;status right by one, because the driver keeps the wire value there and shifts it on completion, so the check must see what the completion path will see. Only REQ_OP_READ is checked, because there the length comes from the sectors the request covers; a passthrough command is built by its submitter, which picks both command and buffer, so the kernel has nothing to compare against.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89480"/>
  </entry>
</feed>
