Menu

Star on GitHub · 3.2k

CVE-2022-50067

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: btrfs: unset reloc control if transaction commit fails in prepare_to_relocate() In btrfs_relocate_block_group(), the rc is allo…

Published Jun 18, 2025CWE-416EPSS 0.22%

Overview

CVE-2022-50067 is a high-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()

In btrfs_relocate_block_group(), the rc is allocated. Then

btrfs_relocate_block_group() calls

relocate_block_group()

prepare_to_relocate()

set_reloc_control()

that assigns rc to the variable fs_info->reloc_ctl. When

prepare_to_relocate() returns, it calls

btrfs_commit_transaction()

btrfs_start_dirty_block_groups()

btrfs_alloc_path()

kmem_cache_zalloc()

which may fail for example (or other errors could happen). When the

failure occurs, btrfs_relocate_block_group() detects the error and frees

rc and doesn't set fs_info->reloc_ctl to NULL. After that, in

btrfs_init_reloc_root(), rc is retrieved from fs_info->reloc_ctl and

then used, which may cause a use-after-free bug.

This possible bug can be triggered by calling btrfs_ioctl_balance()

before calling btrfs_ioctl_defrag().

To fix this possible bug, in prepare_to_relo

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50067?

CVE-2022-50067 is a high-severity vulnerability. It was published on June 18, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2022-50067?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2022-50067?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50067?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50067 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2022

View all