<?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-19T16:59:30.060936+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-23009</id>
    <title>CVE-2026-23009 — xhci: sideband: don't dereference freed ring when removing sideband endpoint</title>
    <updated>2026-11-19T16:59:30.068581+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>xhci: sideband: don't dereference freed ring when removing sideband endpoint</p>
<p>xhci_sideband_remove_endpoint() incorrecly assumes that the endpoint is
running and has a valid transfer ring.</p>
<p>Lianqin reported a crash during suspend/wake-up stress testing, and
found the cause to be dereferencing a non-existing transfer ring
'ep-&gt;ring' during xhci_sideband_remove_endpoint().</p>
<p>The endpoint and its ring may be in unknown state if this function
is called after xHCI was reinitialized in resume (lost power), or if
device is being re-enumerated, disconnected or endpoint already dropped.</p>
<p>Fix this by both removing unnecessary ring access, and by checking
ep-&gt;ring exists before dereferencing it. Also make sure endpoint is
running before attempting to stop it.</p>
<p>Remove the xhci_initialize_ring_info() call during sideband endpoint
removal as is it only initializes ring structure enqueue, dequeue and
cycle state values to their starting values without changing actual
hardware enqueue, dequeue and cycle state. Leaving them out of sync
is worse than leaving it as it is. The endpoint will get freed in after
this in most usecases.</p>
<p>If the (audio) class driver want's to reuse the endpoint after offload
then it is up to the class driver to ensure endpoint is properly set up.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-23009"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8570-1</id>
    <title>USN-8570-1 — linux-gcp-6.17, linux-realtime-6.17 vulnerabilities</title>
    <updated>2026-11-19T16:59:30.068688+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:24.04:LTS: linux-gcp-6.17, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime-6.17</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:
  - Foo-over-UDP (FOU);
  - ARM64 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Drivers core;
  - Null block device driver;
  - Bluetooth drivers;
  - Counter interface drivers;
  - DMA engine subsystem;
  - DPLL subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - On-Chip Interconnect management framework;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - Multiple devices driver;
  - UACCE accelerator framework;
  - MMC subsystem;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PHY drivers;
  - x86 platform drivers;
  - i.MX PM domains;
  - SCSI subsystem;
  - SLIMbus drivers;
  - SPI subsystem;
  - TTY drivers;
  - USB Host Controller drivers;
  - W1 Dallas's 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - EFI Variable file system;
  - Ext4 file system;
  - File systems infrastructure;
  - FUSE (File system in Userspace);
  - Network file systems library;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - SMB network file system;
  - Memory Management;
  - Memory management;
  - Scheduler infrastructure;
  - Tracing infrast…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-8570-1"/>
  </entry>
</feed>
