<?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:36:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-22030 — mm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead()</title>
      <link>https://db.gcve.eu/vuln/cve-2025-22030</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;mm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead()&lt;/p&gt;
&lt;p&gt;Currently, zswap_cpu_comp_dead() calls crypto_free_acomp() while holding
the per-CPU acomp_ctx mutex.  crypto_free_acomp() then holds scomp_lock
(through crypto_exit_scomp_ops_async()).&lt;/p&gt;
&lt;p&gt;On the other hand, crypto_alloc_acomp_node() holds the scomp_lock (through
crypto_scomp_init_tfm()), and then allocates memory.  If the allocation
results in reclaim, we may attempt to hold the per-CPU acomp_ctx mutex.&lt;/p&gt;
&lt;p&gt;The above dependencies can cause an ABBA deadlock.  For example in the
following scenario:&lt;/p&gt;
&lt;p&gt;(1) Task A running on CPU #1:
    crypto_alloc_acomp_node()
      Holds scomp_lock
      Enters reclaim
      Reads per_cpu_ptr(pool-&amp;gt;acomp_ctx, 1)&lt;/p&gt;
&lt;p&gt;(2) Task A is descheduled&lt;/p&gt;
&lt;p&gt;(3) CPU #1 goes offline
    zswap_cpu_comp_dead(CPU #1)
      Holds per_cpu_ptr(pool-&amp;gt;acomp_ctx, 1))
      Calls crypto_free_acomp()
      Waits for scomp_lock&lt;/p&gt;
&lt;p&gt;(4) Task A running on CPU #2:
      Waits for per_cpu_ptr(pool-&amp;gt;acomp_ctx, 1) // Read on CPU #1
      DEADLOCK&lt;/p&gt;
&lt;p&gt;Since there is no requirement to call crypto_free_acomp() with the per-CPU
acomp_ctx mutex held in zswap_cpu_comp_dead(), move it after the mutex is
unlocked.  Also move the acomp_request_free() and kfree() calls for
consistency and to avoid any potential sublte locking dependencies in the
future.&lt;/p&gt;
&lt;p&gt;With this, only setting acomp_ctx fields to NULL occurs with the mutex
held.  This is similar to how zswap_cpu_c…&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;mm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead()&lt;/p&gt;
&lt;p&gt;Currently, zswap_cpu_comp_dead() calls crypto_free_acomp() while holding
the per-CPU acomp_ctx mutex.  crypto_free_acomp() then holds scomp_lock
(through crypto_exit_scomp_ops_async()).&lt;/p&gt;
&lt;p&gt;On the other hand, crypto_alloc_acomp_node() holds the scomp_lock (through
crypto_scomp_init_tfm()), and then allocates memory.  If the allocation
results in reclaim, we may attempt to hold the per-CPU acomp_ctx mutex.&lt;/p&gt;
&lt;p&gt;The above dependencies can cause an ABBA deadlock.  For example in the
following scenario:&lt;/p&gt;
&lt;p&gt;(1) Task A running on CPU #1:
    crypto_alloc_acomp_node()
      Holds scomp_lock
      Enters reclaim
      Reads per_cpu_ptr(pool-&amp;gt;acomp_ctx, 1)&lt;/p&gt;
&lt;p&gt;(2) Task A is descheduled&lt;/p&gt;
&lt;p&gt;(3) CPU #1 goes offline
    zswap_cpu_comp_dead(CPU #1)
      Holds per_cpu_ptr(pool-&amp;gt;acomp_ctx, 1))
      Calls crypto_free_acomp()
      Waits for scomp_lock&lt;/p&gt;
&lt;p&gt;(4) Task A running on CPU #2:
      Waits for per_cpu_ptr(pool-&amp;gt;acomp_ctx, 1) // Read on CPU #1
      DEADLOCK&lt;/p&gt;
&lt;p&gt;Since there is no requirement to call crypto_free_acomp() with the per-CPU
acomp_ctx mutex held in zswap_cpu_comp_dead(), move it after the mutex is
unlocked.  Also move the acomp_request_free() and kfree() calls for
consistency and to avoid any potential sublte locking dependencies in the
future.&lt;/p&gt;
&lt;p&gt;With this, only setting acomp_ctx fields to NULL occurs with the mutex
held.  This is similar to how zswap_cpu_c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-22030</guid>
    </item>
    <item>
      <title>USN-7594-1 — linux, linux-gcp, linux-raspi, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7594-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.04: linux, Ubuntu:25.04: linux-gcp, Ubuntu:25.04: linux-raspi, Ubuntu:25.04: linux-realtime&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:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Bus devices;
  - TPM device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - HSI subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - MCB driver;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Multifunction device drivers;
  - Microchip PCI driver;
  - Intel Management Engine Interface driver;
  - PCI Endpoint Test driver;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Synopsys DesignWare PCIe PMU;
  - Mellanox platform drivers;
  - PWM drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  -…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.04: linux, Ubuntu:25.04: linux-gcp, Ubuntu:25.04: linux-raspi, Ubuntu:25.04: linux-realtime&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:
  - ARM32 architecture;
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Bus devices;
  - TPM device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - HSI subsystem;
  - I2C subsystem;
  - I3C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - MCB driver;
  - Multiple devices driver;
  - Media drivers;
  - MemoryStick subsystem;
  - Multifunction device drivers;
  - Microchip PCI driver;
  - Intel Management Engine Interface driver;
  - PCI Endpoint Test driver;
  - MTD block device drivers;
  - Network drivers;
  - Ethernet bonding driver;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Synopsys DesignWare PCIe PMU;
  - Mellanox platform drivers;
  - PWM drivers;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  -…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7594-1</guid>
    </item>
  </channel>
</rss>
