<?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:48:35.864627+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:19102</id>
    <title>ALSA-2025:19102 — Moderate: kernel security update</title>
    <updated>2026-11-21T00:48:35.880460+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: Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp (CVE-2023-53297)
  * kernel: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (CVE-2025-39817)
  * kernel: Bluetooth: Fix potential use-after-free when clear keys (CVE-2023-53386)
  * kernel: Bluetooth: L2CAP: Fix user-after-free (CVE-2022-50386)
  * kernel: wifi: cfg80211: sme: cap SSID length in __cfg80211_connect_result() (CVE-2025-39849)
  * kernel: scsi: lpfc: Fix buffer free/clear order in deferred receive path (CVE-2025-39841)</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:19102"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2025-22045</id>
    <title>BELL-CVE-2025-22045</title>
    <updated>2026-11-21T00:48:35.880565+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-22045"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0368</id>
    <title>certfr-2025-avi-0368 — 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:48:35.880590+00:00</updated>
    <content>certfr-2025-avi-0368</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0368"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1463</id>
    <title>OESA-2025-1463 — kernel security update</title>
    <updated>2026-11-21T00:48:35.880606+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>PCI/ASPM: Fix link state exit during switch upstream function removal</p>
<p>Before 456d8aa37d0f (&amp;quot;PCI/ASPM: Disable ASPM on MFD function removal to
avoid use-after-free&amp;quot;), we would free the ASPM link only after the last
function on the bus pertaining to the given link was removed.</p>
<p>That was too late. If function 0 is removed before sibling function,
link-&amp;gt;downstream would point to free&amp;apos;d memory after.</p>
<p>After above change, we freed the ASPM parent link state upon any function
removal on the bus pertaining to a given link.</p>
<p>That is too early. If the link is to a PCIe switch with MFD on the upstream
port, then removing functions other than 0 first would free a link which
still remains parent_link to the remaining downstream ports.</p>
<p>The resulting GPFs are especially frequent during hot-unplug, because
pciehp removes devices on the link bus in reverse order.</p>
<p>On that switch, function 0 is the virtual P2P bridge to the internal bus.
Free exactly when function 0 is removed -- before the parent link is
obsolete, but after all subordinate links are gone.</p>
<p>[kwilczynski: commit log](CVE-2024-58093)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>jfs: add check read-only before truncation in jfs_truncate_nolock()</p>
<p>Added a check for &amp;quot;read-only&amp;quot; mode in the `jfs_truncate_nolock`
function to avoid errors…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1463"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22045</id>
    <title>UBUNTU-CVE-2025-22045</title>
    <updated>2026-11-21T00:48:35.880803+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 176 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: x86/mm: Fix flush_tlb_range() when used for zapping normal PMDs On the following path, flush_tlb_range() can be used for zapping normal PMD entries (PMD entries that point to page tables) together with the PTE entries in the pointed-to page table:     collapse_pte_mapped_thp       pmdp_collapse_flush         flush_tlb_range The arm64 version of flush_tlb_range() has a comment describing that it can be used for page table removal, and does not use any last-level invalidation optimizations. Fix the X86 version by making it behave the same way. Currently, X86 only uses this information for the following two purposes, which I think means the issue doesn't have much impact:  - In native_flush_tlb_multi() for checking if lazy TLB CPUs need to be    IPI'd to avoid issues with speculative page table walks.  - In Hyper-V TLB paravirtualization, again for lazy TLB stuff. The patch "x86/mm: only invalidate final translations with INVLPGB" which is currently under review (see &lt;https://lore.kernel.org/all/20241230175550.4046587-13-riel@surriel.com/&gt;) would probably be making the impact of this a lot worse.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22045"/>
  </entry>
</feed>
