<?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 23:39:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99113 — ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99113</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;ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in&lt;/p&gt;
&lt;p&gt;smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION,
that is the whole of struct object_id_info, but writes only 46 of them:&lt;/p&gt;
&lt;p&gt;- objid[] is 16 bytes, and when the volume UUID is not available only
   sizeof(stfs.f_fsid) (8) bytes are copied into it;
 - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only
   strlen(&amp;#34;1.1.0&amp;#34;) (5) bytes are copied into it.&lt;/p&gt;
&lt;p&gt;The response buffer is zeroed on allocation (kvzalloc() in
smb2_allocate_rsp_buf()), so for a standalone request the remaining 31
bytes are zero.  In a compound request they need not be.  The offset of
the next response is advanced by the length pinned for the previous one,
so if a preceding command wrote its reply into the buffer and then
failed, smb2_set_err_rsp() pins only the short error response and the
next reply lands inside the area that has already been written.  Only
the header is cleared there:&lt;/p&gt;
&lt;p&gt;memset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);&lt;/p&gt;
&lt;p&gt;The client then receives up to 31 bytes of a response it was not meant
to see, including one that failed with an access denied error.&lt;/p&gt;
&lt;p&gt;Clear the structure before filling it in.  As a side effect
version_string is now NUL terminated.&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;ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in&lt;/p&gt;
&lt;p&gt;smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION,
that is the whole of struct object_id_info, but writes only 46 of them:&lt;/p&gt;
&lt;p&gt;- objid[] is 16 bytes, and when the volume UUID is not available only
   sizeof(stfs.f_fsid) (8) bytes are copied into it;
 - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only
   strlen(&amp;#34;1.1.0&amp;#34;) (5) bytes are copied into it.&lt;/p&gt;
&lt;p&gt;The response buffer is zeroed on allocation (kvzalloc() in
smb2_allocate_rsp_buf()), so for a standalone request the remaining 31
bytes are zero.  In a compound request they need not be.  The offset of
the next response is advanced by the length pinned for the previous one,
so if a preceding command wrote its reply into the buffer and then
failed, smb2_set_err_rsp() pins only the short error response and the
next reply lands inside the area that has already been written.  Only
the header is cleared there:&lt;/p&gt;
&lt;p&gt;memset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);&lt;/p&gt;
&lt;p&gt;The client then receives up to 31 bytes of a response it was not meant
to see, including one that failed with an access denied error.&lt;/p&gt;
&lt;p&gt;Clear the structure before filling it in.  As a side effect
version_string is now NUL terminated.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99113</guid>
    </item>
    <item>
      <title>USN-9166-1 — linux, linux-aws, linux-gcp, linux-gcp-7.0, linux-gke, linux-ibm, linux-oem-7.0, linux-vmware vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-9166-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-vmware&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:
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - FireWire subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - I2C subsystem;
  - Multiple devices driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Power supply drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - UFS subsystem;
  - File systems infrastructure;
  - Ext4 file system;
  - File system notification infrastructure;
  - NTFS3 file system;
  - OCFS2 file system;
  - SMB network file system;
  - Tracing file system;
  - XFS file system;
  - Kernel futex primitives;
  - Key management;
  - Key Management;
  - VMware vSockets driver;
  - io_uring subsystem;
  - IPC subsystem;
  - Perf events;
  - Kernel exit() syscall;
  - PID namespace;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Tracing infrastructure;
  - Watch queue notification mechanism;
  - Workqueue subsystem;
  - Ethernet bridge;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - IEEE 802.15.4 subsystem;
  - Netfilter;
  - Netlink;
  - RDS protocol;
  - Network traffic control;
  - SCTP protocol;
  - TIPC protocol;
  - SELinux security module;
  - SOF drivers;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-gcp-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-vmware&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:
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - FireWire subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - Microsoft Hyper-V drivers;
  - I2C subsystem;
  - Multiple devices driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Power supply drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - TCM subsystem;
  - UFS subsystem;
  - File systems infrastructure;
  - Ext4 file system;
  - File system notification infrastructure;
  - NTFS3 file system;
  - OCFS2 file system;
  - SMB network file system;
  - Tracing file system;
  - XFS file system;
  - Kernel futex primitives;
  - Key management;
  - Key Management;
  - VMware vSockets driver;
  - io_uring subsystem;
  - IPC subsystem;
  - Perf events;
  - Kernel exit() syscall;
  - PID namespace;
  - printk logging mechanism;
  - Scheduler infrastructure;
  - Tracing infrastructure;
  - Watch queue notification mechanism;
  - Workqueue subsystem;
  - Ethernet bridge;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - IEEE 802.15.4 subsystem;
  - Netfilter;
  - Netlink;
  - RDS protocol;
  - Network traffic control;
  - SCTP protocol;
  - TIPC protocol;
  - SELinux security module;
  - SOF drivers;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-9166-1</guid>
    </item>
  </channel>
</rss>
