CVE-2025-68262 (GCVE-0-2025-68262)
Vulnerability from cvelistv5
Published
2025-12-16 14:45
Modified
2025-12-16 14:45
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: crypto: zstd - fix double-free in per-CPU stream cleanup The crypto/zstd module has a double-free bug that occurs when multiple tfms are allocated and freed. The issue happens because zstd_streams (per-CPU contexts) are freed in zstd_exit() during every tfm destruction, rather than being managed at the module level. When multiple tfms exist, each tfm exit attempts to free the same shared per-CPU streams, resulting in a double-free. This leads to a stack trace similar to: BUG: Bad page state in process kworker/u16:1 pfn:106fd93 page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x106fd93 flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff) page_type: 0xffffffff() raw: 0017ffffc0000000 dead000000000100 dead000000000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: nonzero entire_mapcount Modules linked in: ... CPU: 3 UID: 0 PID: 2506 Comm: kworker/u16:1 Kdump: loaded Tainted: G B Hardware name: ... Workqueue: btrfs-delalloc btrfs_work_helper Call Trace: <TASK> dump_stack_lvl+0x5d/0x80 bad_page+0x71/0xd0 free_unref_page_prepare+0x24e/0x490 free_unref_page+0x60/0x170 crypto_acomp_free_streams+0x5d/0xc0 crypto_acomp_exit_tfm+0x23/0x50 crypto_destroy_tfm+0x60/0xc0 ... Change the lifecycle management of zstd_streams to free the streams only once during module cleanup.
References
Impacted products
Vendor Product Version
Linux Linux Version: f5ad93ffb54119a8dc5e18f070624d4ead586969
Version: f5ad93ffb54119a8dc5e18f070624d4ead586969
Version: f5ad93ffb54119a8dc5e18f070624d4ead586969
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "crypto/zstd.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "dc0f4509b0ed5d82bef78e058db0ac4df04d0695",
              "status": "affected",
              "version": "f5ad93ffb54119a8dc5e18f070624d4ead586969",
              "versionType": "git"
            },
            {
              "lessThan": "e983feaa79de1e46c9087fb9f02fedb0e5397ce6",
              "status": "affected",
              "version": "f5ad93ffb54119a8dc5e18f070624d4ead586969",
              "versionType": "git"
            },
            {
              "lessThan": "48bc9da3c97c15f1ea24934bcb3b736acd30163d",
              "status": "affected",
              "version": "f5ad93ffb54119a8dc5e18f070624d4ead586969",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "crypto/zstd.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.17"
            },
            {
              "lessThan": "6.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.17.*",
              "status": "unaffected",
              "version": "6.17.12",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.1",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.17.12",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.1",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19-rc1",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: zstd - fix double-free in per-CPU stream cleanup\n\nThe crypto/zstd module has a double-free bug that occurs when multiple\ntfms are allocated and freed.\n\nThe issue happens because zstd_streams (per-CPU contexts) are freed in\nzstd_exit() during every tfm destruction, rather than being managed at\nthe module level.  When multiple tfms exist, each tfm exit attempts to\nfree the same shared per-CPU streams, resulting in a double-free.\n\nThis leads to a stack trace similar to:\n\n  BUG: Bad page state in process kworker/u16:1  pfn:106fd93\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x106fd93\n  flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff)\n  page_type: 0xffffffff()\n  raw: 0017ffffc0000000 dead000000000100 dead000000000122 0000000000000000\n  raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000\n  page dumped because: nonzero entire_mapcount\n  Modules linked in: ...\n  CPU: 3 UID: 0 PID: 2506 Comm: kworker/u16:1 Kdump: loaded Tainted: G    B\n  Hardware name: ...\n  Workqueue: btrfs-delalloc btrfs_work_helper\n  Call Trace:\n   \u003cTASK\u003e\n   dump_stack_lvl+0x5d/0x80\n   bad_page+0x71/0xd0\n   free_unref_page_prepare+0x24e/0x490\n   free_unref_page+0x60/0x170\n   crypto_acomp_free_streams+0x5d/0xc0\n   crypto_acomp_exit_tfm+0x23/0x50\n   crypto_destroy_tfm+0x60/0xc0\n   ...\n\nChange the lifecycle management of zstd_streams to free the streams only\nonce during module cleanup."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-12-16T14:45:04.198Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/dc0f4509b0ed5d82bef78e058db0ac4df04d0695"
        },
        {
          "url": "https://git.kernel.org/stable/c/e983feaa79de1e46c9087fb9f02fedb0e5397ce6"
        },
        {
          "url": "https://git.kernel.org/stable/c/48bc9da3c97c15f1ea24934bcb3b736acd30163d"
        }
      ],
      "title": "crypto: zstd - fix double-free in per-CPU stream cleanup",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-68262",
    "datePublished": "2025-12-16T14:45:04.198Z",
    "dateReserved": "2025-12-16T13:41:40.267Z",
    "dateUpdated": "2025-12-16T14:45:04.198Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-68262\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-12-16T15:15:55.697\",\"lastModified\":\"2025-12-18T15:08:06.237\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ncrypto: zstd - fix double-free in per-CPU stream cleanup\\n\\nThe crypto/zstd module has a double-free bug that occurs when multiple\\ntfms are allocated and freed.\\n\\nThe issue happens because zstd_streams (per-CPU contexts) are freed in\\nzstd_exit() during every tfm destruction, rather than being managed at\\nthe module level.  When multiple tfms exist, each tfm exit attempts to\\nfree the same shared per-CPU streams, resulting in a double-free.\\n\\nThis leads to a stack trace similar to:\\n\\n  BUG: Bad page state in process kworker/u16:1  pfn:106fd93\\n  page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x106fd93\\n  flags: 0x17ffffc0000000(node=0|zone=2|lastcpupid=0x1fffff)\\n  page_type: 0xffffffff()\\n  raw: 0017ffffc0000000 dead000000000100 dead000000000122 0000000000000000\\n  raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000\\n  page dumped because: nonzero entire_mapcount\\n  Modules linked in: ...\\n  CPU: 3 UID: 0 PID: 2506 Comm: kworker/u16:1 Kdump: loaded Tainted: G    B\\n  Hardware name: ...\\n  Workqueue: btrfs-delalloc btrfs_work_helper\\n  Call Trace:\\n   \u003cTASK\u003e\\n   dump_stack_lvl+0x5d/0x80\\n   bad_page+0x71/0xd0\\n   free_unref_page_prepare+0x24e/0x490\\n   free_unref_page+0x60/0x170\\n   crypto_acomp_free_streams+0x5d/0xc0\\n   crypto_acomp_exit_tfm+0x23/0x50\\n   crypto_destroy_tfm+0x60/0xc0\\n   ...\\n\\nChange the lifecycle management of zstd_streams to free the streams only\\nonce during module cleanup.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/48bc9da3c97c15f1ea24934bcb3b736acd30163d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/dc0f4509b0ed5d82bef78e058db0ac4df04d0695\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e983feaa79de1e46c9087fb9f02fedb0e5397ce6\",\"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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.