<?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-19T17:37:14.350975+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-23130</id>
    <title>CVE-2026-23130 — wifi: ath12k: fix dead lock while flushing management frames</title>
    <updated>2026-11-19T17:37:14.357795+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>wifi: ath12k: fix dead lock while flushing management frames</p>
<p>Commit [1] converted the management transmission work item into a
wiphy work. Since a wiphy work can only run under wiphy lock
protection, a race condition happens in below scenario:</p>
<p>1. a management frame is queued for transmission.
2. ath12k_mac_op_flush() gets called to flush pending frames associated
   with the hardware (i.e, vif being NULL). Then in ath12k_mac_flush()
   the process waits for the transmission done.
3. Since wiphy lock has been taken by the flush process, the transmission
   work item has no chance to run, hence the dead lock.</p>
<p>&gt;From user view, this dead lock results in below issue:</p>
<p>wlp8s0: authenticate with xxxxxx (local address=xxxxxx)
 wlp8s0: send auth to xxxxxx (try 1/3)
 wlp8s0: authenticate with xxxxxx (local address=xxxxxx)
 wlp8s0: send auth to xxxxxx (try 1/3)
 wlp8s0: authenticated
 wlp8s0: associate with xxxxxx (try 1/3)
 wlp8s0: aborting association with xxxxxx by local choice (Reason: 3=DEAUTH_LEAVING)
 ath12k_pci 0000:08:00.0: failed to flush mgmt transmit queue, mgmt pkts pending 1</p>
<p>The dead lock can be avoided by invoking wiphy_work_flush() to proactively
run the queued work item. Note actually it is already present in
ath12k_mac_op_flush(), however it does not protect the case where vif
being NULL. Hence move it ahead to cover this case as well.</p>
<p>Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00302-QCAHMTSW…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-23130"/>
  </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-19T17:37:14.357888+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>
