{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68262 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68262 is an use after free vulnerability in Linux, published on 16 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2025-68262 and fix it if it is affected.\n\nWhat it is: CVE-2025-68262 is an use after free vulnerability in Linux, published on 16 Dec 2025. \nExploitation: There is no known exploitation of CVE-2025-68262 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68262/ (Markdown: https://insights.sbomify.com/CVE-2025-68262/index.md)","id":"CVE-2025-68262","markdown":"https://insights.sbomify.com/CVE-2025-68262/index.md","name":"CVE-2025-68262","record":{"aliases":["BELL-CVE-2025-68262","DEBIAN-CVE-2025-68262","GHSA-3792-937m-5pm4","UBUNTU-CVE-2025-68262"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A double-free vulnerability in the Linux kernel's zstd crypto module allows attackers to cause denial of service or potentially execute code.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"crypto: zstd - fix double-free in per-CPU stream cleanup","id":"CVE-2025-68262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"ksmbd: ipc: fix use-after-free in ipc_msg_send_request","id":"CVE-2025-68263"},"packages":[],"prev":{"headline":"ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock()","id":"CVE-2025-68261"},"products":["Linux"],"published":"2025-12-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A double-free vulnerability in the Linux kernel's zstd crypto module allows attackers to cause denial of service or potentially execute code.","url":"https://insights.sbomify.com/CVE-2025-68262/"}