<?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:53:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-52923 — ipc: limit next_id allocation to the valid ID range</title>
      <link>https://db.gcve.eu/vuln/cve-2026-52923</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 8.8 Telecommunications Update Service, Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions, Red Hat Enterprise Linux 9 and 5 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipc: limit next_id allocation to the valid ID range&lt;/p&gt;
&lt;p&gt;The checkpoint/restore sysctl path can request the next SysV IPC id
through ids-&amp;gt;next_id.  ipc_idr_alloc() currently forwards that request to
idr_alloc() with an open-ended upper bound.&lt;/p&gt;
&lt;p&gt;If the valid tail of the SysV IPC id space is full, the allocation can
spill beyond ipc_mni.  The returned SysV IPC id still uses the normal
index encoding, so later lookup and removal can target the wrong slot. 
This leaves the real IDR entry behind and breaks the IDR state for the
object.&lt;/p&gt;
&lt;p&gt;The bug is in ipc_idr_alloc() in the checkpoint/restore path.&lt;/p&gt;
&lt;p&gt;1. ids-&amp;gt;next_id is passed to:&lt;/p&gt;
&lt;p&gt;idr_alloc(&amp;amp;ids-&amp;gt;ipcs_idr, new, ipcid_to_idx(next_id), 0, ...)&lt;/p&gt;
&lt;p&gt;2. The zero upper bound makes the allocation effectively open-ended.
   Once the valid SysV IPC tail is occupied, idr_alloc() can spill past
   ipc_mni and allocate an entry beyond the valid IPC id range.&lt;/p&gt;
&lt;p&gt;3. The new object id is still encoded with the narrower SysV IPC index
   width:&lt;/p&gt;
&lt;p&gt;new-&amp;gt;id = (new-&amp;gt;seq &amp;lt;&amp;lt; ipcmni_seq_shift()) + idx&lt;/p&gt;
&lt;p&gt;4. Later removal goes through ipc_rmid(), which uses:&lt;/p&gt;
&lt;p&gt;ipcid_to_idx(ipcp-&amp;gt;id)&lt;/p&gt;
&lt;p&gt;That truncates the real IDR index. An object actually stored at a
   high index can then be removed as if it lived at a low in-range
   index.&lt;/p&gt;
&lt;p&gt;5. For shared memory, shm_destroy() frees the current object anyway, but
   the real high IDR slot is left behind as a dangling pointer.&lt;/p&gt;
&lt;p&gt;6. A subsequent w…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On, Red Hat Enterprise Linux 8.8 Telecommunications Update Service, Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions, Red Hat Enterprise Linux 9 and 5 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipc: limit next_id allocation to the valid ID range&lt;/p&gt;
&lt;p&gt;The checkpoint/restore sysctl path can request the next SysV IPC id
through ids-&amp;gt;next_id.  ipc_idr_alloc() currently forwards that request to
idr_alloc() with an open-ended upper bound.&lt;/p&gt;
&lt;p&gt;If the valid tail of the SysV IPC id space is full, the allocation can
spill beyond ipc_mni.  The returned SysV IPC id still uses the normal
index encoding, so later lookup and removal can target the wrong slot. 
This leaves the real IDR entry behind and breaks the IDR state for the
object.&lt;/p&gt;
&lt;p&gt;The bug is in ipc_idr_alloc() in the checkpoint/restore path.&lt;/p&gt;
&lt;p&gt;1. ids-&amp;gt;next_id is passed to:&lt;/p&gt;
&lt;p&gt;idr_alloc(&amp;amp;ids-&amp;gt;ipcs_idr, new, ipcid_to_idx(next_id), 0, ...)&lt;/p&gt;
&lt;p&gt;2. The zero upper bound makes the allocation effectively open-ended.
   Once the valid SysV IPC tail is occupied, idr_alloc() can spill past
   ipc_mni and allocate an entry beyond the valid IPC id range.&lt;/p&gt;
&lt;p&gt;3. The new object id is still encoded with the narrower SysV IPC index
   width:&lt;/p&gt;
&lt;p&gt;new-&amp;gt;id = (new-&amp;gt;seq &amp;lt;&amp;lt; ipcmni_seq_shift()) + idx&lt;/p&gt;
&lt;p&gt;4. Later removal goes through ipc_rmid(), which uses:&lt;/p&gt;
&lt;p&gt;ipcid_to_idx(ipcp-&amp;gt;id)&lt;/p&gt;
&lt;p&gt;That truncates the real IDR index. An object actually stored at a
   high index can then be removed as if it lived at a low in-range
   index.&lt;/p&gt;
&lt;p&gt;5. For shared memory, shm_destroy() frees the current object anyway, but
   the real high IDR slot is left behind as a dangling pointer.&lt;/p&gt;
&lt;p&gt;6. A subsequent w…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-52923</guid>
    </item>
    <item>
      <title>USN-8566-1 — linux, linux-gcp, linux-gke, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8566-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&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:
  - PSP security protocol;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - DRBD Distributed Replicated Block Device drivers;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Bus devices;
  - Character device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - EDAC drivers;
  - EFI core;
  - FWCTL subsystem;
  - GPU drivers;
  - HID subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Mailbox framework;
  - Multiple devices driver;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - MediaTek network drivers;
  - NVME drivers;
  - PCI subsystem;…&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-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&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:
  - PSP security protocol;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - DRBD Distributed Replicated Block Device drivers;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Bus devices;
  - Character device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - EDAC drivers;
  - EFI core;
  - FWCTL subsystem;
  - GPU drivers;
  - HID subsystem;
  - I3C subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Mailbox framework;
  - Multiple devices driver;
  - Media drivers;
  - NVIDIA Tegra memory controller driver;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - MediaTek network drivers;
  - NVME drivers;
  - PCI subsystem;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8566-1</guid>
    </item>
  </channel>
</rss>
