<?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:28:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39961 — iommu/amd/pgtbl: Fix possible race while increase page table level</title>
      <link>https://db.gcve.eu/vuln/cve-2025-39961</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;iommu/amd/pgtbl: Fix possible race while increase page table level&lt;/p&gt;
&lt;p&gt;The AMD IOMMU host page table implementation supports dynamic page table levels
(up to 6 levels), starting with a 3-level configuration that expands based on
IOVA address. The kernel maintains a root pointer and current page table level
to enable proper page table walks in alloc_pte()/fetch_pte() operations.&lt;/p&gt;
&lt;p&gt;The IOMMU IOVA allocator initially starts with 32-bit address and onces its
exhuasted it switches to 64-bit address (max address is determined based
on IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU
driver increases page table level.&lt;/p&gt;
&lt;p&gt;But in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads
pgtable-&amp;gt;[root/mode] without lock. So its possible that in exteme corner case,
when increase_address_space() is updating pgtable-&amp;gt;[root/mode], fetch_pte()
reads wrong page table level (pgtable-&amp;gt;mode). It does compare the value with
level encoded in page table and returns NULL. This will result is
iommu_unmap ops to fail and upper layer may retry/log WARN_ON.&lt;/p&gt;
&lt;p&gt;CPU 0                                         CPU 1
------                                       ------
map pages                                    unmap pages
alloc_pte() -&amp;gt; increase_address_space()      iommu_v1_unmap_pages() -&amp;gt; fetch_pte()
  pgtable-&amp;gt;root = pte (new root value)
                                             READ pgtable-&amp;gt;[mode/root]
					       Reads…&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;iommu/amd/pgtbl: Fix possible race while increase page table level&lt;/p&gt;
&lt;p&gt;The AMD IOMMU host page table implementation supports dynamic page table levels
(up to 6 levels), starting with a 3-level configuration that expands based on
IOVA address. The kernel maintains a root pointer and current page table level
to enable proper page table walks in alloc_pte()/fetch_pte() operations.&lt;/p&gt;
&lt;p&gt;The IOMMU IOVA allocator initially starts with 32-bit address and onces its
exhuasted it switches to 64-bit address (max address is determined based
on IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU
driver increases page table level.&lt;/p&gt;
&lt;p&gt;But in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads
pgtable-&amp;gt;[root/mode] without lock. So its possible that in exteme corner case,
when increase_address_space() is updating pgtable-&amp;gt;[root/mode], fetch_pte()
reads wrong page table level (pgtable-&amp;gt;mode). It does compare the value with
level encoded in page table and returns NULL. This will result is
iommu_unmap ops to fail and upper layer may retry/log WARN_ON.&lt;/p&gt;
&lt;p&gt;CPU 0                                         CPU 1
------                                       ------
map pages                                    unmap pages
alloc_pte() -&amp;gt; increase_address_space()      iommu_v1_unmap_pages() -&amp;gt; fetch_pte()
  pgtable-&amp;gt;root = pte (new root value)
                                             READ pgtable-&amp;gt;[mode/root]
					       Reads…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-39961</guid>
    </item>
    <item>
      <title>USN-8095-1 — linux, linux-aws, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-hwe-6.8, linux-ibm, linux-ibm-6.8, linux-lowl…</title>
      <link>https://db.gcve.eu/vuln/usn-8095-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-hwe-6.8, Ubuntu:22.04:LTS: linux-ibm-6.8, Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.8, Ubuntu:22.04:LTS: linux-oracle-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop and 3 more&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&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:
  - ARM64 architecture;
  - MIPS architecture;
  - Nios II architecture;
  - PA-RISC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Sun Sparc architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Xtensa architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - ATM drivers;
  - Drivers core;
  - Block device driver;
  - Network block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Hardware random number generator core;
  - Character device driver;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - EFI core;
  - Intel Stratix 10 firmware drivers;
  - GPU drivers;
  - HID subsystem;
  - CoreSight HW tracing drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-hwe-6.8, Ubuntu:22.04:LTS: linux-ibm-6.8, Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.8, Ubuntu:22.04:LTS: linux-oracle-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-gke, Ubuntu:24.04:LTS: linux-gkeop and 3 more&lt;/p&gt;
&lt;p&gt;Qualys discovered that several vulnerabilities existed in the AppArmor
Linux kernel Security Module (LSM). An unprivileged local attacker could
use these issues to load, replace, and remove arbitrary AppArmor profiles
causing denial of service, exposure of sensitive information (kernel
memory), local privilege escalation, or possibly escape a container.
(LP: #2143853)&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:
  - ARM64 architecture;
  - MIPS architecture;
  - Nios II architecture;
  - PA-RISC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Sun Sparc architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Xtensa architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - ATM drivers;
  - Drivers core;
  - Block device driver;
  - Network block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Hardware random number generator core;
  - Character device driver;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - ARM SCMI message protocol;
  - EFI core;
  - Intel Stratix 10 firmware drivers;
  - GPU drivers;
  - HID subsystem;
  - CoreSight HW tracing drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8095-1</guid>
    </item>
  </channel>
</rss>
