<?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-21T03:58:36.702087+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/bell-cve-2025-22015</id>
    <title>BELL-CVE-2025-22015</title>
    <updated>2026-11-21T03:58:36.714491+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-22015"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0333</id>
    <title>certfr-2025-avi-0333 — 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-21T03:58:36.714749+00:00</updated>
    <content>certfr-2025-avi-0333</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0333"/>
  </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-21T03:58:36.714783+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-22015</id>
    <title>UBUNTU-CVE-2025-22015</title>
    <updated>2026-11-21T03:58:36.714915+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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 110 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: mm/migrate: fix shmem xarray update during migration A shmem folio can be either in page cache or in swap cache, but not at the same time.  Namely, once it is in swap cache, folio-&gt;mapping should be NULL, and the folio is no longer in a shmem mapping. In __folio_migrate_mapping(), to determine the number of xarray entries to update, folio_test_swapbacked() is used, but that conflates shmem in page cache case and shmem in swap cache case.  It leads to xarray multi-index entry corruption, since it turns a sibling entry to a normal entry during xas_store() (see [1] for a userspace reproduction).  Fix it by only using folio_test_swapcache() to determine whether xarray is storing swap cache entries or not to choose the right number of xarray entries to update. [1] https://lore.kernel.org/linux-mm/Z8idPCkaJW1IChjT@casper.infradead.org/ Note: In __split_huge_page(), folio_test_anon() &amp;&amp; folio_test_swapcache() is used to get swap_cache address space, but that ignores the shmem folio in swap cache case.  It could lead to NULL pointer dereferencing when a in-swap-cache shmem folio is split at __xa_store(), since !folio_test_anon() is true and folio-&gt;mapping is NULL.  But fortunately, its caller split_huge_page_to_list_to_order() bails out early with EBUSY when folio-&gt;mapping is NULL.  So no need to take care of it here.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22015"/>
  </entry>
</feed>
