<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T18:06:06.613612+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2025-38084</id>
    <title>CVE-2025-38084 — mm/hugetlb: unshare page tables during VMA split, not before</title>
    <updated>2026-11-19T18:06:06.696052+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/hugetlb: unshare page tables during VMA split, not before</p>
<p>Currently, __split_vma() triggers hugetlb page table unsharing through
vm_ops-&gt;may_split().  This happens before the VMA lock and rmap locks are
taken - which is too early, it allows racing VMA-locked page faults in our
process and racing rmap walks from other processes to cause page tables to
be shared again before we actually perform the split.</p>
<p>Fix it by explicitly calling into the hugetlb unshare logic from
__split_vma() in the same place where THP splitting also happens.  At that
point, both the VMA and the rmap(s) are write-locked.</p>
<p>An annoying detail is that we can now call into the helper
hugetlb_unshare_pmds() from two different locking contexts:</p>
<p>1. from hugetlb_split(), holding:
    - mmap lock (exclusively)
    - VMA lock
    - file rmap lock (exclusively)
2. hugetlb_unshare_all_pmds(), which I think is designed to be able to
   call us with only the mmap lock held (in shared mode), but currently
   only runs while holding mmap lock (exclusively) and VMA lock</p>
<p>Backporting note:
This commit fixes a racy protection that was introduced in commit
b30c14cd6102 ("hugetlb: unshare some PMDs when splitting VMAs"); that
commit claimed to fix an issue introduced in 5.13, but it should actually
also go all the way back.</p>
<p>[jannh@google.com: v2]</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2025-38084"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-7774-1</id>
    <title>USN-7774-1 — linux, linux-aws, linux-aws-5.15, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-hwe-5.15, linux-ibm, linux-i…</title>
    <updated>2026-11-19T18:06:06.696170+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-gcp-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-intel-iotg-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-aws, Ubuntu:22.04:LTS: linux-gcp and 10 more</p>
<p>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:
  - ARM64 architecture;
  - PowerPC architecture;
  - x86 architecture;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - Network block device driver;
  - Bus devices;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - Multiple devices driver;
  - Media drivers;
  - VMware VMCI Driver;
  - MMC subsystem;
  - MTD block device drivers;
  - Network drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - PTP clock framework;
  - RapidIO drivers;
  - Voltage and Current Regulator drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - ASPEED SoC drivers;
  - TCM subsystem;
  - Thermal drivers;
  - Thunderbolt and USB4 drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB Gadget drivers;
  - Renesas USBHS Controller drivers;
  - USB Type-C support driver;
  - Virtio Host (VHOST) subsystem;
  - Backlight driver;
  - Framebuffer layer;
  - BTRFS file system;
  - File systems infrastructure;
  - Ext4 file system;
  - F2FS file system;
  - JFFS2 file system;
  - JFS file system;
  - Network file system (NFS) client;
  - Network file syst…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-7774-1"/>
  </entry>
</feed>
