CVE-2022-50571
BaseFortify
Publication date: 2025-10-22
Last updated on: 2025-10-22
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 in the Linux kernel's btrfs filesystem code. It occurs when there is a failure loading the free space cache. The code attempts to free up resources by calling a function that requires a specific lock to be held, but in this case, the lock is not held because the cleanup is done on a temporary control structure. This leads to a warning and potential instability. The fix involves calling a different cleanup function that only removes entries without affecting discardable statistics, avoiding the need for the lock.
How can this vulnerability impact me? :
This vulnerability can cause warnings and potential instability or crashes in the Linux kernel when the btrfs filesystem tries to load its free space cache and encounters an error. This could lead to filesystem issues or degraded system reliability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel warning related to btrfs discard operations, specifically a stack trace involving btrfs_discard_update_discardable and free space cache loading failures. Detection can be done by monitoring the system kernel logs for warnings or errors matching the described stack trace. You can use commands such as 'dmesg | grep btrfs_discard_update_discardable' or 'journalctl -k | grep btrfs_discard_update_discardable' to detect occurrences of this issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this issue is fixed, as the vulnerability is resolved by calling __btrfs_remove_free_space_cache_locked instead of the previous function to avoid improper locking. Until an update is applied, monitoring kernel logs for the warning and avoiding workloads that heavily use btrfs discard operations may reduce exposure.