CVE-2025-68262
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a double-free bug in the Linux kernel's crypto/zstd module. It occurs when multiple tfms (transforms) are allocated and freed. The problem arises because the per-CPU zstd_streams are freed during each tfm destruction instead of being managed at the module level. As a result, when multiple tfms exist, each tfm exit tries to free the same shared per-CPU streams multiple times, causing a double-free error that can lead to kernel crashes or instability.
How can this vulnerability impact me? :
This vulnerability can cause system instability or crashes due to the double-free error in the kernel's memory management. Specifically, it can lead to bad page states and kernel stack traces indicating memory corruption. This can affect the reliability and availability of systems running the vulnerable Linux kernel, potentially causing unexpected reboots or service interruptions.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring system logs for stack traces indicating a double-free error in the crypto/zstd module. Specifically, look for kernel messages containing 'BUG: Bad page state' and call traces involving crypto_acomp_free_streams and crypto_destroy_tfm. You can use commands like 'dmesg | grep -i "BUG: Bad page state"' or 'journalctl -k | grep -i "crypto_acomp_free_streams"' to find relevant logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the crypto/zstd module's double-free bug is fixed. The fix changes the lifecycle management of zstd_streams to ensure streams are freed only once during module cleanup. Until the update is applied, avoid workloads that allocate and free multiple tfms in the crypto/zstd module to reduce the risk of triggering the bug.