NVD / CVE Program· CNA Linux

CVE-2022-50067: btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 5d741afed0bac206640cc64d77b97853283cf719, 78f8c2370e3d33e35f23bdc648653d779aeacb6e, 85f02d6c856b9f3a0acf5219de6e32f58b9778eb.

Low priority for now. Upgrade to Linux Linux 5d741afed0bac206640cc64d77b97853283cf719, 78f8c2370e3d33e35f23bdc648653d779aeacb6e, 85f02d6c856b9f3a0acf5219de6e32f58b9778eb or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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_relocate(), check if btrfs_commit_transaction() fails. If the failure occurs, unset_reloc_control() is called to set fs_info->reloc_ctl to NULL. The error log in our fault-injection testing is shown as follows: [ 58.751070] BUG: KASAN: use-after-free in btrfs_init_reloc_root+0x7ca/0x920 [btrfs] ... [ 58.753577] Call Trace: ... [ 58.755800] kasan_report+0x45/0x60 [ 58.756066] btrfs_init_reloc_root+0x7ca/0x920 [btrfs] [ 58.757304] record_root_in_trans+0x792/0xa10 [btrfs] [ 58.757748] btrfs_record_root_in_trans+0x463/0x4f0 [btrfs] [ 58.758231] start_transaction+0x896/0x2950 [btrfs] [ 58.758661] btrfs_defrag_root+0x250/0xc00 [btrfs] [ 58.759083] btrfs_ioctl_defrag+0x467/0xa00 [btrfs] [ 58.759513] btrfs_ioctl+0x3c95/0x114e0 [btrfs] ... [ 58.768510] Allocated by task 23683: [ 58.768777] ____kasan_kmalloc+0xb5/0xf0 [ 58.769069] __kmalloc+0x227/0x3d0 [ 58.769325] alloc_reloc_control+0x10a/0x3d0 [btrfs] [ 58.769755] btrfs_relocate_block_group+0x7aa/0x1e20 [btrfs] [ 58.770228] btrfs_relocate_chunk+0xf1/0x760 [btrfs] [ 58.770655] __btrfs_balance+0x1326/0x1f10 [btrfs] [ 58.771071] btrfs_balance+0x3150/0x3d30 [btrfs] [ 58.771472] btrfs_ioctl_balance+0xd84/0x1410 [btrfs] [ 58.771902] btrfs_ioctl+0x4caa/0x114e0 [btrfs] ... [ 58.773337] Freed by task 23683: ... [ 58.774815] kfree+0xda/0x2b0 [ 58.775038] free_reloc_control+0x1d6/0x220 [btrfs] [ 58.775465] btrfs_relocate_block_group+0x115c/0x1e20 [btrfs] [ 58.775944] btrfs_relocate_chunk+0xf1/0x760 [btrfs] [ 58.776369] __btrfs_balance+0x1326/0x1f10 [btrfs] [ 58.776784] btrfs_balance+0x3150/0x3d30 [btrfs] [ 58.777185] btrfs_ioctl_balance+0xd84/0x1410 [btrfs] [ 58.777621] btrfs_ioctl+0x4caa/0x114e0 [btrfs] ...

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: Jun 18, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 13th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernelbefore 4.14.318
linux linux kernel4.15 and later · before 4.19.286
linux linux kernel4.20 and later · before 5.4.247
linux linux kernel5.5 and later · before 5.10.184
linux linux kernel5.11 and later · before 5.15.63
linux linux kernel5.16 and later · before 5.19.4
linux linux kernel6.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5.13affected
- 1a5353475df8fcaf200fecc9e961a3900d15e891 and later · before ff0e8ed8dfb584575cffc1561f17a1d094e8565baffected · git
- 499d29bf151951399367ba83645abfdb429a3af9 and later · before dcb11fe0a0a9cca2b7425191b9bf30dc29f2ad0faffected · git
- 4223d91ca1b5bf3928e5722c3c6b3fdb49250ab3 and later · before 8e546674031fc1576da501e27a8fd165222e5a37affected · git
- 6f371623f315c26100e603c2e8837cdbe130f9e0 and later · before b60e862e133f646f19023ece1d476d630a660de1affected · git
- fb686c6824dd6294ca772b92424b8fba666e7d00 and later · before 78f8c2370e3d33e35f23bdc648653d779aeacb6eaffected · git
- fb686c6824dd6294ca772b92424b8fba666e7d00 and later · before 5d741afed0bac206640cc64d77b97853283cf719affected · git
- fb686c6824dd6294ca772b92424b8fba666e7d00 and later · before 85f02d6c856b9f3a0acf5219de6e32f58b9778ebaffected · git
- before 5.13not affected · semver
- 5.15.63 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.0.2-1	6.0.2-1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-default	before 3.0.101-108.186.1	3.0.101-108.186.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-ec2	before 3.0.101-108.186.1	3.0.101-108.186.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-source	before 3.0.101-108.186.1	3.0.101-108.186.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-syms	before 3.0.101-108.186.1	3.0.101-108.186.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-trace	before 3.0.101-108.186.1	3.0.101-108.186.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	kernel-xen	before 3.0.101-108.186.1	3.0.101-108.186.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2022-50065Jun 18, 2025 · virtio_net: fix memory leak inside XPD_TX with mergeable
22Monitor
← EarlierCVE-2022-50066Jun 18, 2025 · net: atlantic: fix aq_vec index out of range error
31Monitor
Later →CVE-2022-50068Jun 18, 2025 · drm/ttm: Fix dummy res NULL ptr deref bug
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	5d741afed0bac206640cc64d77b97853283cf719	Vendor (CNA)
Linux Linux	78f8c2370e3d33e35f23bdc648653d779aeacb6e	Vendor (CNA)
Linux Linux	85f02d6c856b9f3a0acf5219de6e32f58b9778eb	Vendor (CNA)
Linux Linux	8e546674031fc1576da501e27a8fd165222e5a37	Vendor (CNA)
Linux Linux	b60e862e133f646f19023ece1d476d630a660de1	Vendor (CNA)
Linux Linux	dcb11fe0a0a9cca2b7425191b9bf30dc29f2ad0f	Vendor (CNA)
Linux Linux	ff0e8ed8dfb584575cffc1561f17a1d094e8565b	Vendor (CNA)
debian:linux	6.0.2-1 · Debian:12	Package registry (OSV)
suse:kernel-default	3.0.101-108.186.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-ec2	3.0.101-108.186.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-source	3.0.101-108.186.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-syms	3.0.101-108.186.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-trace	3.0.101-108.186.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)
suse:kernel-xen	3.0.101-108.186.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/5d741afed0bac206640cc64d77b97853283cf719

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records