<?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:26:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45990 — slub: fix data loss and overflow in krealloc()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-45990</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;slub: fix data loss and overflow in krealloc()&lt;/p&gt;
&lt;p&gt;Commit 2cd8231796b5 (&amp;#34;mm/slub: allow to set node and align in
k[v]realloc&amp;#34;) introduced the ability to force a reallocation if the
original object does not satisfy new alignment or NUMA node, even when
the object is being shrunk.&lt;/p&gt;
&lt;p&gt;This introduced two bugs in the reallocation fallback path:&lt;/p&gt;
&lt;p&gt;1. Data loss during NUMA migration: The jump to &amp;#39;alloc_new&amp;#39; happens
   before &amp;#39;ks&amp;#39; and &amp;#39;orig_size&amp;#39; are initialized. As a result, the
   memcpy() in the &amp;#39;alloc_new&amp;#39; block would copy 0 bytes into the new
   allocation.&lt;/p&gt;
&lt;p&gt;2. Buffer overflow during shrinking: When shrinking an object while
   forcing a new alignment, &amp;#39;new_size&amp;#39; is smaller than the old size.
   However, the memcpy() used the old size (&amp;#39;orig_size ?: ks&amp;#39;), leading
   to an out-of-bounds write.&lt;/p&gt;
&lt;p&gt;The same overflow bug exists in the kvrealloc() fallback path, where the
old bucket size ksize(p) is copied into the new buffer without being
bounded by the new size.&lt;/p&gt;
&lt;p&gt;A simple reproducer:&lt;/p&gt;
&lt;p&gt;// e.g. add to lkdtm as KREALLOC_SHRINK_OVERFLOW
	while (1) {
		void *p = kmalloc(128, GFP_KERNEL);
		p = krealloc_node_align(p, 64, 256, GFP_KERNEL, NUMA_NO_NODE);
		kfree(p);
	}&lt;/p&gt;
&lt;p&gt;demonstrates the issue:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KFENCE: out-of-bounds write in memcpy_orig+0x68/0x130&lt;/p&gt;
&lt;p&gt;Out-of-bounds write at 0xffff8883ad757038 (120B right of kfence-#47):
   memcpy_orig+0x68/0x130
   krea…&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;slub: fix data loss and overflow in krealloc()&lt;/p&gt;
&lt;p&gt;Commit 2cd8231796b5 (&amp;#34;mm/slub: allow to set node and align in
k[v]realloc&amp;#34;) introduced the ability to force a reallocation if the
original object does not satisfy new alignment or NUMA node, even when
the object is being shrunk.&lt;/p&gt;
&lt;p&gt;This introduced two bugs in the reallocation fallback path:&lt;/p&gt;
&lt;p&gt;1. Data loss during NUMA migration: The jump to &amp;#39;alloc_new&amp;#39; happens
   before &amp;#39;ks&amp;#39; and &amp;#39;orig_size&amp;#39; are initialized. As a result, the
   memcpy() in the &amp;#39;alloc_new&amp;#39; block would copy 0 bytes into the new
   allocation.&lt;/p&gt;
&lt;p&gt;2. Buffer overflow during shrinking: When shrinking an object while
   forcing a new alignment, &amp;#39;new_size&amp;#39; is smaller than the old size.
   However, the memcpy() used the old size (&amp;#39;orig_size ?: ks&amp;#39;), leading
   to an out-of-bounds write.&lt;/p&gt;
&lt;p&gt;The same overflow bug exists in the kvrealloc() fallback path, where the
old bucket size ksize(p) is copied into the new buffer without being
bounded by the new size.&lt;/p&gt;
&lt;p&gt;A simple reproducer:&lt;/p&gt;
&lt;p&gt;// e.g. add to lkdtm as KREALLOC_SHRINK_OVERFLOW
	while (1) {
		void *p = kmalloc(128, GFP_KERNEL);
		p = krealloc_node_align(p, 64, 256, GFP_KERNEL, NUMA_NO_NODE);
		kfree(p);
	}&lt;/p&gt;
&lt;p&gt;demonstrates the issue:&lt;/p&gt;
&lt;p&gt;==================================================================
  BUG: KFENCE: out-of-bounds write in memcpy_orig+0x68/0x130&lt;/p&gt;
&lt;p&gt;Out-of-bounds write at 0xffff8883ad757038 (120B right of kfence-#47):
   memcpy_orig+0x68/0x130
   krea…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-45990</guid>
    </item>
    <item>
      <title>USN-8488-1 — linux, linux-aws, linux-gcp, linux-ibm, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8488-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&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;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Character device driver;
  - TPM device driver;
  - Hardware crypto device drivers;
  - EDAC drivers;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - IBM Advanced System Management driver;
  - MTD block device drivers;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NTB driver;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PCI subsystem;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SPI subsystem;
  - Realtek RTL8723BS SDIO drivers;
  - SM750 framebuffer staging driver;
  - Thermal drivers;
  - USB Gadget drivers;
  - USB over IP driver;
  - VFIO drivers;
  - Framebuffer layer;
  - 9P distributed file system;
  - AFS file…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&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;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Character device driver;
  - TPM device driver;
  - Hardware crypto device drivers;
  - EDAC drivers;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - IBM Advanced System Management driver;
  - MTD block device drivers;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NTB driver;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PCI subsystem;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SPI subsystem;
  - Realtek RTL8723BS SDIO drivers;
  - SM750 framebuffer staging driver;
  - Thermal drivers;
  - USB Gadget drivers;
  - USB over IP driver;
  - VFIO drivers;
  - Framebuffer layer;
  - 9P distributed file system;
  - AFS file…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8488-1</guid>
    </item>
  </channel>
</rss>
