<?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-19T17:38:00.731665+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-2026-23077</id>
    <title>CVE-2026-23077 — mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge</title>
    <updated>2026-11-19T17:38:00.795209+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/vma: fix anon_vma UAF on mremap() faulted, unfaulted merge</p>
<p>Patch series "mm/vma: fix anon_vma UAF on mremap() faulted, unfaulted
merge", v2.</p>
<p>Commit 879bca0a2c4f ("mm/vma: fix incorrectly disallowed anonymous VMA
merges") introduced the ability to merge previously unavailable VMA merge
scenarios.</p>
<p>However, it is handling merges incorrectly when it comes to mremap() of a
faulted VMA adjacent to an unfaulted VMA.  The issues arise in three
cases:</p>
<p>1. Previous VMA unfaulted:</p>
<p>copied -----|
                          v
	|-----------|.............|
	| unfaulted |(faulted VMA)|
	|-----------|.............|
	     prev</p>
<p>2. Next VMA unfaulted:</p>
<p>copied -----|
                          v
	            |.............|-----------|
	            |(faulted VMA)| unfaulted |
                    |.............|-----------|
		                      next</p>
<p>3. Both adjacent VMAs unfaulted:</p>
<p>copied -----|
                          v
	|-----------|.............|-----------|
	| unfaulted |(faulted VMA)| unfaulted |
	|-----------|.............|-----------|
	     prev                      next</p>
<p>This series fixes each of these cases, and introduces self tests to assert
that the issues are corrected.</p>
<p>I also test a further case which was already handled, to assert that my
changes continues to correctly handle it:</p>
<p>4. prev unfaulted, next faulted:</p>
<p>copied -----|…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-23077"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8570-1</id>
    <title>USN-8570-1 — linux-gcp-6.17, linux-realtime-6.17 vulnerabilities</title>
    <updated>2026-11-19T17:38:00.795323+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: linux-gcp-6.17, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.17</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:
  - Foo-over-UDP (FOU);
  - ARM64 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Drivers core;
  - Null block device driver;
  - Bluetooth drivers;
  - Counter interface drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - On-Chip Interconnect management framework;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - Multiple devices driver;
  - UACCE accelerator framework;
  - MMC subsystem;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PHY drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - SLIMbus drivers;
  - SPI subsystem;
  - TTY drivers;
  - USB Host Controller drivers;
  - W1 Dallas's 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - EFI Variable file system;
  - Ext4 file system;
  - File systems infrastructure;
  - FUSE (File system in Userspace);
  - Network file systems library;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - SMB network file system;
  - Memory Management;
  - Memory management;
  - Scheduler infrastructure;
  - Tracing infrast…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-8570-1"/>
  </entry>
</feed>
