<?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 17:43:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40181 — x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP</title>
      <link>https://db.gcve.eu/vuln/cve-2025-40181</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;x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP&lt;/p&gt;
&lt;p&gt;When running as an SNP or TDX guest under KVM, force the legacy PCI hole,
i.e. memory between Top of Lower Usable DRAM and 4GiB, to be mapped as UC
via a forced variable MTRR range.&lt;/p&gt;
&lt;p&gt;In most KVM-based setups, legacy devices such as the HPET and TPM are
enumerated via ACPI.  ACPI enumeration includes a Memory32Fixed entry, and
optionally a SystemMemory descriptor for an OperationRegion, e.g. if the
device needs to be accessed via a Control Method.&lt;/p&gt;
&lt;p&gt;If a SystemMemory entry is present, then the kernel&amp;#39;s ACPI driver will
auto-ioremap the region so that it can be accessed at will.  However, the
ACPI spec doesn&amp;#39;t provide a way to enumerate the memory type of
SystemMemory regions, i.e. there&amp;#39;s no way to tell software that a region
must be mapped as UC vs. WB, etc.  As a result, Linux&amp;#39;s ACPI driver always
maps SystemMemory regions using ioremap_cache(), i.e. as WB on x86.&lt;/p&gt;
&lt;p&gt;The dedicated device drivers however, e.g. the HPET driver and TPM driver,
want to map their associated memory as UC or WC, as accessing PCI devices
using WB is unsupported.&lt;/p&gt;
&lt;p&gt;On bare metal and non-CoCO, the conflicting requirements &amp;#34;work&amp;#34; as firmware
configures the PCI hole (and other device memory) to be UC in the MTRRs.
So even though the ACPI mappings request WB, they are forced to UC- in the
kernel&amp;#39;s tracking due to the kernel properly handling the MTRR overrides,
and thu…&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;x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP&lt;/p&gt;
&lt;p&gt;When running as an SNP or TDX guest under KVM, force the legacy PCI hole,
i.e. memory between Top of Lower Usable DRAM and 4GiB, to be mapped as UC
via a forced variable MTRR range.&lt;/p&gt;
&lt;p&gt;In most KVM-based setups, legacy devices such as the HPET and TPM are
enumerated via ACPI.  ACPI enumeration includes a Memory32Fixed entry, and
optionally a SystemMemory descriptor for an OperationRegion, e.g. if the
device needs to be accessed via a Control Method.&lt;/p&gt;
&lt;p&gt;If a SystemMemory entry is present, then the kernel&amp;#39;s ACPI driver will
auto-ioremap the region so that it can be accessed at will.  However, the
ACPI spec doesn&amp;#39;t provide a way to enumerate the memory type of
SystemMemory regions, i.e. there&amp;#39;s no way to tell software that a region
must be mapped as UC vs. WB, etc.  As a result, Linux&amp;#39;s ACPI driver always
maps SystemMemory regions using ioremap_cache(), i.e. as WB on x86.&lt;/p&gt;
&lt;p&gt;The dedicated device drivers however, e.g. the HPET driver and TPM driver,
want to map their associated memory as UC or WC, as accessing PCI devices
using WB is unsupported.&lt;/p&gt;
&lt;p&gt;On bare metal and non-CoCO, the conflicting requirements &amp;#34;work&amp;#34; as firmware
configures the PCI hole (and other device memory) to be UC in the MTRRs.
So even though the ACPI mappings request WB, they are forced to UC- in the
kernel&amp;#39;s tracking due to the kernel properly handling the MTRR overrides,
and thu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-40181</guid>
    </item>
    <item>
      <title>USN-8029-1 — linux, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8029-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: linux, Ubuntu:25.10: linux-raspi, Ubuntu:25.10: linux-realtime&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;
  - x86 architecture;
  - Xtensa architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Hardware random number generator core;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Device frequency scaling framework;
  - ARM SCMI message protocol;
  - GPIO subsystem;
  - GPU drivers;
  - Hardware monitoring drivers;
  - HW tracing;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - IOMMU subsystem;
  - ISDN/mISDN subsystem;
  - Mailbox framework;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - PCI Endpoint Test driver;
  - VMware Balloon Driver;
  - MOST (Media Oriented Systems Transport) drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: linux, Ubuntu:25.10: linux-raspi, Ubuntu:25.10: linux-realtime&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;
  - x86 architecture;
  - Xtensa architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Drivers core;
  - Network block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Hardware random number generator core;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Device frequency scaling framework;
  - ARM SCMI message protocol;
  - GPIO subsystem;
  - GPU drivers;
  - Hardware monitoring drivers;
  - HW tracing;
  - InfiniBand drivers;
  - Input Device (Miscellaneous) drivers;
  - IOMMU subsystem;
  - ISDN/mISDN subsystem;
  - Mailbox framework;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - PCI Endpoint Test driver;
  - VMware Balloon Driver;
  - MOST (Media Oriented Systems Transport) drivers;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8029-1</guid>
    </item>
  </channel>
</rss>
