Vulnerability · Published Apr 16, 2025 · Assigned by Linux

CVE-2025-22030mm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead()

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.2%top 90.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: mm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead() 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()). 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. The above dependencies can cause an ABBA deadlock. For example in the following scenario: (1) Task A running on CPU #1: crypto_alloc_acomp_node() Holds scomp_lock Enters reclaim Reads per_cpu_ptr(pool->acomp_ctx, 1) (2) Task A is descheduled (3) CPU #1 goes offline zswap_cpu_comp_dead(CPU #1) Holds per_cpu_ptr(pool->acomp_ctx, 1)) Calls crypto_free_acomp() Waits for scomp_lock (4) Task A running on CPU #2: Waits for per_cpu_ptr(pool->acomp_ctx, 1) // Read on CPU #1 DEADLOCK 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. With this, only setting acomp_ctx fields to NULL occurs with the mutex held. This is similar to how zswap_cpu_comp_prepare() only initializes acomp_ctx fields with the mutex held, after performing all allocations before holding the mutex. Opportunistically, move the NULL check on acomp_ctx so that it takes place before the mutex dereference.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.25-1DEBIAN-CVE-2025-22030
Debian:14linux6.12.25-1DEBIAN-CVE-2025-22030
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1018.18~24.04.1UBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1016.16~24.04.1UBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:24.04:LTSlinux-hwe-6.116.11.0-28.28~24.04.1UBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.116.11.0-1015.16~24.04.2UBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1012.12UBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-22030
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1024.24UBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-22030
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-22030
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-22030

Affected products (as reported)

VendorProductVersions
Linux Linux 8d29ff5d50304daa41dc3cfdda4a9d1e46cf5be1 – before 747e3eec1d7d124ea90ed3d7b85369df8b4e36d212dcb0ef540629a281533f9dedc1b6b8e14cfb65 – before a8d18000e9d2d97aaf105f5f9b3b0e8a6fbf8b9612dcb0ef540629a281533f9dedc1b6b8e14cfb65 – before 717d9c35deff6c33235693171bacbb03e9643fa412dcb0ef540629a281533f9dedc1b6b8e14cfb65 – before c11bcbc0a517acf69282c8225059b2a8ac5fe6286.12.12 – before 6.12.23
Linux Linux 6.13

References