CVE-2025-22030 (GCVE-0-2025-22030)
Vulnerability from cvelistv5
Published
2025-04-16 14:11
Modified
2025-05-26 05:16
Severity ?
Summary
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.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/717d9c35deff6c33235693171bacbb03e9643fa4
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/747e3eec1d7d124ea90ed3d7b85369df8b4e36d2
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/a8d18000e9d2d97aaf105f5f9b3b0e8a6fbf8b96
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/c11bcbc0a517acf69282c8225059b2a8ac5fe628
Impacted products
Vendor Product Version
Linux Linux Version: 8d29ff5d50304daa41dc3cfdda4a9d1e46cf5be1
Version: 12dcb0ef540629a281533f9dedc1b6b8e14cfb65
Version: 12dcb0ef540629a281533f9dedc1b6b8e14cfb65
Version: 12dcb0ef540629a281533f9dedc1b6b8e14cfb65
 Create a notification for this product.
   Linux Linux Version: 6.13
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/zswap.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "747e3eec1d7d124ea90ed3d7b85369df8b4e36d2",
              "status": "affected",
              "version": "8d29ff5d50304daa41dc3cfdda4a9d1e46cf5be1",
              "versionType": "git"
            },
            {
              "lessThan": "a8d18000e9d2d97aaf105f5f9b3b0e8a6fbf8b96",
              "status": "affected",
              "version": "12dcb0ef540629a281533f9dedc1b6b8e14cfb65",
              "versionType": "git"
            },
            {
              "lessThan": "717d9c35deff6c33235693171bacbb03e9643fa4",
              "status": "affected",
              "version": "12dcb0ef540629a281533f9dedc1b6b8e14cfb65",
              "versionType": "git"
            },
            {
              "lessThan": "c11bcbc0a517acf69282c8225059b2a8ac5fe628",
              "status": "affected",
              "version": "12dcb0ef540629a281533f9dedc1b6b8e14cfb65",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/zswap.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.13"
            },
            {
              "lessThan": "6.13",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.23",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.14.*",
              "status": "unaffected",
              "version": "6.14.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.15",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.23",
                  "versionStartIncluding": "6.12.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.11",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14.2",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead()\n\nCurrently, zswap_cpu_comp_dead() calls crypto_free_acomp() while holding\nthe per-CPU acomp_ctx mutex.  crypto_free_acomp() then holds scomp_lock\n(through crypto_exit_scomp_ops_async()).\n\nOn the other hand, crypto_alloc_acomp_node() holds the scomp_lock (through\ncrypto_scomp_init_tfm()), and then allocates memory.  If the allocation\nresults in reclaim, we may attempt to hold the per-CPU acomp_ctx mutex.\n\nThe above dependencies can cause an ABBA deadlock.  For example in the\nfollowing scenario:\n\n(1) Task A running on CPU #1:\n    crypto_alloc_acomp_node()\n      Holds scomp_lock\n      Enters reclaim\n      Reads per_cpu_ptr(pool-\u003eacomp_ctx, 1)\n\n(2) Task A is descheduled\n\n(3) CPU #1 goes offline\n    zswap_cpu_comp_dead(CPU #1)\n      Holds per_cpu_ptr(pool-\u003eacomp_ctx, 1))\n      Calls crypto_free_acomp()\n      Waits for scomp_lock\n\n(4) Task A running on CPU #2:\n      Waits for per_cpu_ptr(pool-\u003eacomp_ctx, 1) // Read on CPU #1\n      DEADLOCK\n\nSince there is no requirement to call crypto_free_acomp() with the per-CPU\nacomp_ctx mutex held in zswap_cpu_comp_dead(), move it after the mutex is\nunlocked.  Also move the acomp_request_free() and kfree() calls for\nconsistency and to avoid any potential sublte locking dependencies in the\nfuture.\n\nWith this, only setting acomp_ctx fields to NULL occurs with the mutex\nheld.  This is similar to how zswap_cpu_comp_prepare() only initializes\nacomp_ctx fields with the mutex held, after performing all allocations\nbefore holding the mutex.\n\nOpportunistically, move the NULL check on acomp_ctx so that it takes place\nbefore the mutex dereference."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-26T05:16:57.089Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/747e3eec1d7d124ea90ed3d7b85369df8b4e36d2"
        },
        {
          "url": "https://git.kernel.org/stable/c/a8d18000e9d2d97aaf105f5f9b3b0e8a6fbf8b96"
        },
        {
          "url": "https://git.kernel.org/stable/c/717d9c35deff6c33235693171bacbb03e9643fa4"
        },
        {
          "url": "https://git.kernel.org/stable/c/c11bcbc0a517acf69282c8225059b2a8ac5fe628"
        }
      ],
      "title": "mm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-22030",
    "datePublished": "2025-04-16T14:11:50.625Z",
    "dateReserved": "2024-12-29T08:45:45.808Z",
    "dateUpdated": "2025-05-26T05:16:57.089Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-22030\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-04-16T15:15:55.607\",\"lastModified\":\"2025-04-17T20:22:16.240\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmm: zswap: fix crypto_free_acomp() deadlock in zswap_cpu_comp_dead()\\n\\nCurrently, zswap_cpu_comp_dead() calls crypto_free_acomp() while holding\\nthe per-CPU acomp_ctx mutex.  crypto_free_acomp() then holds scomp_lock\\n(through crypto_exit_scomp_ops_async()).\\n\\nOn the other hand, crypto_alloc_acomp_node() holds the scomp_lock (through\\ncrypto_scomp_init_tfm()), and then allocates memory.  If the allocation\\nresults in reclaim, we may attempt to hold the per-CPU acomp_ctx mutex.\\n\\nThe above dependencies can cause an ABBA deadlock.  For example in the\\nfollowing scenario:\\n\\n(1) Task A running on CPU #1:\\n    crypto_alloc_acomp_node()\\n      Holds scomp_lock\\n      Enters reclaim\\n      Reads per_cpu_ptr(pool-\u003eacomp_ctx, 1)\\n\\n(2) Task A is descheduled\\n\\n(3) CPU #1 goes offline\\n    zswap_cpu_comp_dead(CPU #1)\\n      Holds per_cpu_ptr(pool-\u003eacomp_ctx, 1))\\n      Calls crypto_free_acomp()\\n      Waits for scomp_lock\\n\\n(4) Task A running on CPU #2:\\n      Waits for per_cpu_ptr(pool-\u003eacomp_ctx, 1) // Read on CPU #1\\n      DEADLOCK\\n\\nSince there is no requirement to call crypto_free_acomp() with the per-CPU\\nacomp_ctx mutex held in zswap_cpu_comp_dead(), move it after the mutex is\\nunlocked.  Also move the acomp_request_free() and kfree() calls for\\nconsistency and to avoid any potential sublte locking dependencies in the\\nfuture.\\n\\nWith this, only setting acomp_ctx fields to NULL occurs with the mutex\\nheld.  This is similar to how zswap_cpu_comp_prepare() only initializes\\nacomp_ctx fields with the mutex held, after performing all allocations\\nbefore holding the mutex.\\n\\nOpportunistically, move the NULL check on acomp_ctx so that it takes place\\nbefore the mutex dereference.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/717d9c35deff6c33235693171bacbb03e9643fa4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/747e3eec1d7d124ea90ed3d7b85369df8b4e36d2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a8d18000e9d2d97aaf105f5f9b3b0e8a6fbf8b96\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c11bcbc0a517acf69282c8225059b2a8ac5fe628\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.