CVE-2022-50090
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's Btrfs filesystem arises because the system uses a fixed maximum extent size (BTRFS_MAX_EXTENT_SIZE) to estimate metadata reservation, while on zoned filesystems, the actual data write size is limited by max_zone_append_size and large extents are split accordingly. If BTRFS_MAX_EXTENT_SIZE is larger than max_zone_append_size, the number of extents increases significantly, causing the reserved metadata space to run out. This can lead to warnings and potential failures in metadata reservation during writes, especially in environments with limited RAM and disabled metadata over-commit.
How can this vulnerability impact me? :
The vulnerability can cause the Linux kernel to run out of reserved metadata space during writes on zoned filesystems, leading to warnings and potential write failures. This can affect system stability and data integrity during file operations, particularly on systems with small RAM and specific configurations that disable metadata over-commit.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for specific warning messages related to BTRFS metadata reservation failures. Look for kernel log entries containing warnings such as 'BTRFS: block rsv 1 returned -28' and 'WARNING: CPU: ... btrfs_use_block_rsv'. You can use the command 'dmesg | grep -i btrfs' or 'journalctl -k | grep -i btrfs' to search for these messages in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability is resolved, which replaces BTRFS_MAX_EXTENT_SIZE with fs_info->max_extent_size to properly handle metadata reservation on zoned filesystems. Additionally, avoid disabling metadata over-commit on systems with small RAM to prevent running out of reserved metadata bytes.