<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 18:52:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21984 — mm: fix kernel BUG when userfaultfd_move encounters swapcache</title>
      <link>https://db.gcve.eu/vuln/cve-2025-21984</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: fix kernel BUG when userfaultfd_move encounters swapcache&lt;/p&gt;
&lt;p&gt;userfaultfd_move() checks whether the PTE entry is present or a
swap entry.&lt;/p&gt;
&lt;p&gt;- If the PTE entry is present, move_present_pte() handles folio
  migration by setting:&lt;/p&gt;
&lt;p&gt;src_folio-&amp;gt;index = linear_page_index(dst_vma, dst_addr);&lt;/p&gt;
&lt;p&gt;- If the PTE entry is a swap entry, move_swap_pte() simply copies
  the PTE to the new dst_addr.&lt;/p&gt;
&lt;p&gt;This approach is incorrect because, even if the PTE is a swap entry,
it can still reference a folio that remains in the swap cache.&lt;/p&gt;
&lt;p&gt;This creates a race window between steps 2 and 4.
 1. add_to_swap: The folio is added to the swapcache.
 2. try_to_unmap: PTEs are converted to swap entries.
 3. pageout: The folio is written back.
 4. Swapcache is cleared.
If userfaultfd_move() occurs in the window between steps 2 and 4,
after the swap PTE has been moved to the destination, accessing the
destination triggers do_swap_page(), which may locate the folio in
the swapcache. However, since the folio&amp;#39;s index has not been updated
to match the destination VMA, do_swap_page() will detect a mismatch.&lt;/p&gt;
&lt;p&gt;This can result in two critical issues depending on the system
configuration.&lt;/p&gt;
&lt;p&gt;If KSM is disabled, both small and large folios can trigger a BUG
during the add_rmap operation due to:&lt;/p&gt;
&lt;p&gt;page_pgoff(folio, page) != linear_page_index(vma, address)&lt;/p&gt;
&lt;p&gt;[   13.336953] page: refcount:6 mapcount:1 mapping:00000000f43db19c index:0xffffaf150 pfn:0x4667c
[…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: fix kernel BUG when userfaultfd_move encounters swapcache&lt;/p&gt;
&lt;p&gt;userfaultfd_move() checks whether the PTE entry is present or a
swap entry.&lt;/p&gt;
&lt;p&gt;- If the PTE entry is present, move_present_pte() handles folio
  migration by setting:&lt;/p&gt;
&lt;p&gt;src_folio-&amp;gt;index = linear_page_index(dst_vma, dst_addr);&lt;/p&gt;
&lt;p&gt;- If the PTE entry is a swap entry, move_swap_pte() simply copies
  the PTE to the new dst_addr.&lt;/p&gt;
&lt;p&gt;This approach is incorrect because, even if the PTE is a swap entry,
it can still reference a folio that remains in the swap cache.&lt;/p&gt;
&lt;p&gt;This creates a race window between steps 2 and 4.
 1. add_to_swap: The folio is added to the swapcache.
 2. try_to_unmap: PTEs are converted to swap entries.
 3. pageout: The folio is written back.
 4. Swapcache is cleared.
If userfaultfd_move() occurs in the window between steps 2 and 4,
after the swap PTE has been moved to the destination, accessing the
destination triggers do_swap_page(), which may locate the folio in
the swapcache. However, since the folio&amp;#39;s index has not been updated
to match the destination VMA, do_swap_page() will detect a mismatch.&lt;/p&gt;
&lt;p&gt;This can result in two critical issues depending on the system
configuration.&lt;/p&gt;
&lt;p&gt;If KSM is disabled, both small and large folios can trigger a BUG
during the add_rmap operation due to:&lt;/p&gt;
&lt;p&gt;page_pgoff(folio, page) != linear_page_index(vma, address)&lt;/p&gt;
&lt;p&gt;[   13.336953] page: refcount:6 mapcount:1 mapping:00000000f43db19c index:0xffffaf150 pfn:0x4667c
[…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-21984</guid>
    </item>
    <item>
      <title>USN-7605-1 — linux, linux-aws, linux-gcp, linux-gcp-6.11, linux-hwe-6.11, linux-oracle, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7605-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly verify the target namespace when handling
upcalls. An attacker could use this to expose sensitive information.
(CVE-2025-2312)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bus devices;
  - AMD CDX bus driver;
  - Clock framework and drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - Mellanox network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - VideoCore services drivers;
  - Thermal drivers;
  - USB DSL drivers;
  - USB Host Controller drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Connector System Software Interface driver;
  - Virtio Host (VHOST) subsystem;
  - Fr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-6.11, Ubuntu:24.04:LTS: linux-hwe-6.11&lt;/p&gt;
&lt;p&gt;It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly verify the target namespace when handling
upcalls. An attacker could use this to expose sensitive information.
(CVE-2025-2312)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bus devices;
  - AMD CDX bus driver;
  - Clock framework and drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - Qualcomm firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - Mellanox network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SLIMbus drivers;
  - QCOM SoC drivers;
  - VideoCore services drivers;
  - Thermal drivers;
  - USB DSL drivers;
  - USB Host Controller drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C Connector System Software Interface driver;
  - Virtio Host (VHOST) subsystem;
  - Fr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7605-1</guid>
    </item>
  </channel>
</rss>
