<?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:57:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21991 — x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes</title>
      <link>https://db.gcve.eu/vuln/cve-2025-21991</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/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes&lt;/p&gt;
&lt;p&gt;Currently, load_microcode_amd() iterates over all NUMA nodes, retrieves their
CPU masks and unconditionally accesses per-CPU data for the first CPU of each
mask.&lt;/p&gt;
&lt;p&gt;According to Documentation/admin-guide/mm/numaperf.rst:&lt;/p&gt;
&lt;p&gt;&amp;#34;Some memory may share the same node as a CPU, and others are provided as
  memory only nodes.&amp;#34;&lt;/p&gt;
&lt;p&gt;Therefore, some node CPU masks may be empty and wouldn&amp;#39;t have a &amp;#34;first CPU&amp;#34;.&lt;/p&gt;
&lt;p&gt;On a machine with far memory (and therefore CPU-less NUMA nodes):
- cpumask_of_node(nid) is 0
- cpumask_first(0) is CONFIG_NR_CPUS
- cpu_data(CONFIG_NR_CPUS) accesses the cpu_info per-CPU array at an
  index that is 1 out of bounds&lt;/p&gt;
&lt;p&gt;This does not have any security implications since flashing microcode is
a privileged operation but I believe this has reliability implications by
potentially corrupting memory while flashing a microcode update.&lt;/p&gt;
&lt;p&gt;When booting with CONFIG_UBSAN_BOUNDS=y on an AMD machine that flashes
a microcode update. I get the following splat:&lt;/p&gt;
&lt;p&gt;UBSAN: array-index-out-of-bounds in arch/x86/kernel/cpu/microcode/amd.c:X:Y
  index 512 is out of range for type &amp;#39;unsigned long[512]&amp;#39;
  [...]
  Call Trace:
   dump_stack
   __ubsan_handle_out_of_bounds
   load_microcode_amd
   request_microcode_amd
   reload_store
   kernfs_fop_write_iter
   vfs_write
   ksys_write
   do_syscall_64
   entry_SYSCALL_64_after_hwframe&lt;/p&gt;
&lt;p&gt;Change the loop to go o…&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/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes&lt;/p&gt;
&lt;p&gt;Currently, load_microcode_amd() iterates over all NUMA nodes, retrieves their
CPU masks and unconditionally accesses per-CPU data for the first CPU of each
mask.&lt;/p&gt;
&lt;p&gt;According to Documentation/admin-guide/mm/numaperf.rst:&lt;/p&gt;
&lt;p&gt;&amp;#34;Some memory may share the same node as a CPU, and others are provided as
  memory only nodes.&amp;#34;&lt;/p&gt;
&lt;p&gt;Therefore, some node CPU masks may be empty and wouldn&amp;#39;t have a &amp;#34;first CPU&amp;#34;.&lt;/p&gt;
&lt;p&gt;On a machine with far memory (and therefore CPU-less NUMA nodes):
- cpumask_of_node(nid) is 0
- cpumask_first(0) is CONFIG_NR_CPUS
- cpu_data(CONFIG_NR_CPUS) accesses the cpu_info per-CPU array at an
  index that is 1 out of bounds&lt;/p&gt;
&lt;p&gt;This does not have any security implications since flashing microcode is
a privileged operation but I believe this has reliability implications by
potentially corrupting memory while flashing a microcode update.&lt;/p&gt;
&lt;p&gt;When booting with CONFIG_UBSAN_BOUNDS=y on an AMD machine that flashes
a microcode update. I get the following splat:&lt;/p&gt;
&lt;p&gt;UBSAN: array-index-out-of-bounds in arch/x86/kernel/cpu/microcode/amd.c:X:Y
  index 512 is out of range for type &amp;#39;unsigned long[512]&amp;#39;
  [...]
  Call Trace:
   dump_stack
   __ubsan_handle_out_of_bounds
   load_microcode_amd
   request_microcode_amd
   reload_store
   kernfs_fop_write_iter
   vfs_write
   ksys_write
   do_syscall_64
   entry_SYSCALL_64_after_hwframe&lt;/p&gt;
&lt;p&gt;Change the loop to go o…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-21991</guid>
    </item>
    <item>
      <title>USN-7585-1 — linux, linux-aws, linux-aws-5.4, linux-azure, linux-gcp, linux-gcp-5.4, linux-ibm, linux-ibm-5.4, linux-kvm, linux-orac…</title>
      <link>https://db.gcve.eu/vuln/usn-7585-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-ibm-5.4, Ubuntu:Pro:18.04:LTS: linux-oracle-5.4, Ubuntu:Pro:20.04:LTS: linux, Ubuntu:Pro:20.04:LTS: linux-aws, Ubuntu:Pro:20.04:LTS: linux-azure, Ubuntu:Pro:20.04:LTS: linux-gcp, Ubuntu:Pro:20.04:LTS: linux-ibm, Ubuntu:Pro:20.04:LTS: linux-kvm and 2 more&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:
  - PowerPC architecture;
  - x86 architecture;
  - iSCSI Boot Firmware Table Attributes driver;
  - GPU drivers;
  - HID subsystem;
  - InfiniBand drivers;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - NTB driver;
  - PCI subsystem;
  - SCSI subsystem;
  - Thermal drivers;
  - JFS file system;
  - File systems infrastructure;
  - Tracing infrastructure;
  - 802.1Q VLAN protocol;
  - Asynchronous Transfer Mode (ATM) subsystem;
  - Bluetooth subsystem;
  - IPv6 networking;
  - Netfilter;
  - Network traffic control;
  - Sun RPC protocol;
  - USB sound devices;
(CVE-2025-22007, CVE-2025-21959, CVE-2025-22021, CVE-2025-22063,
CVE-2025-22045, CVE-2024-58093, CVE-2022-49636, CVE-2025-22020,
CVE-2024-53168, CVE-2025-22071, CVE-2025-39735, CVE-2025-21991,
CVE-2025-21992, CVE-2025-21996, CVE-2025-22035, CVE-2023-53034,
CVE-2025-22054, CVE-2025-23136, CVE-2025-22073, CVE-2024-56551,
CVE-2025-22005, CVE-2025-37937, CVE-2021-47211, CVE-2025-22086,
CVE-2025-21956, CVE-2025-38637, CVE-2025-22004, CVE-2025-22018,
CVE-2025-22079, CVE-2025-21957, CVE-2025-21993)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-ibm-5.4, Ubuntu:Pro:18.04:LTS: linux-oracle-5.4, Ubuntu:Pro:20.04:LTS: linux, Ubuntu:Pro:20.04:LTS: linux-aws, Ubuntu:Pro:20.04:LTS: linux-azure, Ubuntu:Pro:20.04:LTS: linux-gcp, Ubuntu:Pro:20.04:LTS: linux-ibm, Ubuntu:Pro:20.04:LTS: linux-kvm and 2 more&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:
  - PowerPC architecture;
  - x86 architecture;
  - iSCSI Boot Firmware Table Attributes driver;
  - GPU drivers;
  - HID subsystem;
  - InfiniBand drivers;
  - Media drivers;
  - MemoryStick subsystem;
  - Network drivers;
  - NTB driver;
  - PCI subsystem;
  - SCSI subsystem;
  - Thermal drivers;
  - JFS file system;
  - File systems infrastructure;
  - Tracing infrastructure;
  - 802.1Q VLAN protocol;
  - Asynchronous Transfer Mode (ATM) subsystem;
  - Bluetooth subsystem;
  - IPv6 networking;
  - Netfilter;
  - Network traffic control;
  - Sun RPC protocol;
  - USB sound devices;
(CVE-2025-22007, CVE-2025-21959, CVE-2025-22021, CVE-2025-22063,
CVE-2025-22045, CVE-2024-58093, CVE-2022-49636, CVE-2025-22020,
CVE-2024-53168, CVE-2025-22071, CVE-2025-39735, CVE-2025-21991,
CVE-2025-21992, CVE-2025-21996, CVE-2025-22035, CVE-2023-53034,
CVE-2025-22054, CVE-2025-23136, CVE-2025-22073, CVE-2024-56551,
CVE-2025-22005, CVE-2025-37937, CVE-2021-47211, CVE-2025-22086,
CVE-2025-21956, CVE-2025-38637, CVE-2025-22004, CVE-2025-22018,
CVE-2025-22079, CVE-2025-21957, CVE-2025-21993)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7585-1</guid>
    </item>
  </channel>
</rss>
