CVE-2022-50379

linux: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between quota enable and quota r...

CVE-2022-50379 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50379, released September 18, 2025. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
4.7
medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0011
1st percentile

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix race between quota enable and quota rescan ioctl When enabling quotas, at btrfs_quota_enable(), after committing the transaction, we change fs_info->quota_root to point to the quota root we created and set BTRFS_FS_QUOTA_ENABLED at fs_info->flags. Then we try to start the qgroup rescan worker, first by initializing it with a call to qgroup_rescan_init() - however if that fails we end up freeing the quota root but we leave fs_info->quota_root still pointing to it, this can later result in a use-after-free somewhere else. We have previously set the flags BTRFS_FS_QUOTA_ENABLED and BTRFS_QGROUP_STATUS_FLAG_ON, so we can only fail with -EINPROGRESS at btrfs_quota_enable(), which is possible if someone already called the quota rescan ioctl, and therefore started the rescan worker. So fix this by ignoring an -EINPROGRESS and asserting we can't get any other error.

Where it's fixed

ProductFixed inFixReleased
Linux
linux · Debian 12.15 (bookworm) 6.0.3-1 DEBIAN-CVE-2022-50379 Sep 18, 2025
linux · Debian 13.5 (trixie) 6.0.3-1 DEBIAN-CVE-2022-50379 Sep 18, 2025
linux · Debian 14 6.0.3-1 DEBIAN-CVE-2022-50379 Sep 18, 2025

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.