<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T23:39:06.105325+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-99124</id>
    <title>CVE-2026-99124 — s390/pci: Fix leak of uninitialized kernel data in SCLP report</title>
    <updated>2026-11-19T23:39:06.130230+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>s390/pci: Fix leak of uninitialized kernel data in SCLP report</p>
<p>While report_error_write() checks that the provided buffer is at least
as large as the header struct, but not that it is large enough to
contain the report with the length claimed by report-&gt;length. If
user-space provides a short buffer, meaning a larger report-&gt;length than
the actually written payload, up to around 4K of kernel data from past
the kmalloc(len + 1) sized buffer allocated in kernfs_fop_write_iter()
will leak into the SCLP report.</p>
<p>However, as the entity processing the SCLP is privileged and able to
access at least the page including the report, this does not leak data
that entity could not access but it is still an out of bounds read and
a malformed error report that should be rejected.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99124"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-9166-1</id>
    <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>
    <updated>2026-11-19T23:39:06.130304+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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;…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-9166-1"/>
  </entry>
</feed>
