<?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:45:59.368563+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-2025:15008</id>
    <title>ALSA-2025:15008 — Moderate: kernel security update</title>
    <updated>2026-11-21T00:45:59.390229+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: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction (CVE-2025-38211)
  * kernel: scsi: lpfc: Use memcpy() for BIOS version (CVE-2025-38332)
  * kernel: tipc: Fix use-after-free in tipc_conn_close() (CVE-2025-38464)
  * kernel: net/sched: sch_qfq: Fix race condition on qfq_aggregate (CVE-2025-38477)</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-2025:15008"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2025-38332</id>
    <title>BELL-CVE-2025-38332</title>
    <updated>2026-11-21T00:45:59.390348+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-38332"/>
  </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-21T00:45:59.390373+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-21T00:45:59.390390+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-38332</id>
    <title>UBUNTU-CVE-2025-38332</title>
    <updated>2026-11-21T00:45:59.390662+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 186 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38332"/>
  </entry>
</feed>
