CVE-2022-50379btrfs: fix race between quota enable and quota rescan ioctl
- 4.7MediumCVSS base score
- 0.11%Exploitation in 30 daysEPSS · top 99% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 8 months later
· 8 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.11% · top 99% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.
Affected products
- affected 5d23515be66904fa3b1b5d6bd72d2199cd2447ab – < c97f6d528c3f1c83a6b792a8a7928c236c80b8fe
- affected 5d23515be66904fa3b1b5d6bd72d2199cd2447ab – < 26b7c0ac49a3eea15559c9d84863736a6d1164b4
- affected 5d23515be66904fa3b1b5d6bd72d2199cd2447ab – < 47b5ffe86332af95f0f52be0a63d4da7c2b37b55
- affected 5d23515be66904fa3b1b5d6bd72d2199cd2447ab – < 4b996a3014ef014af8f97b60c35f5289210a4720
- affected 5d23515be66904fa3b1b5d6bd72d2199cd2447ab – < 0efd9dfc00d677a1d0929319a6103cb2dfc41c22
- affected 5d23515be66904fa3b1b5d6bd72d2199cd2447ab – < 6c22f86dd221eba0c7af645b1af73dcbc04ee27b
- affected 5d23515be66904fa3b1b5d6bd72d2199cd2447ab – < 331cd9461412e103d07595a10289de90004ac890
- affected 4.17
- unaffected < 4.17
- unaffected 4.19.262 – ≤ 4.19.*
- unaffected 5.4.220 – ≤ 5.4.*
- unaffected 5.10.150 – ≤ 5.10.*
- unaffected 5.15.75 – ≤ 5.15.*
- unaffected 5.19.17 – ≤ 5.19.*
- unaffected 6.0.3 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/c97f6d528c3f1c83a6b792a8a7928c236c80b8fe (opens in a new tab)
- https://git.kernel.org/stable/c/26b7c0ac49a3eea15559c9d84863736a6d1164b4 (opens in a new tab)
- https://git.kernel.org/stable/c/47b5ffe86332af95f0f52be0a63d4da7c2b37b55 (opens in a new tab)
- https://git.kernel.org/stable/c/4b996a3014ef014af8f97b60c35f5289210a4720 (opens in a new tab)
- https://git.kernel.org/stable/c/0efd9dfc00d677a1d0929319a6103cb2dfc41c22 (opens in a new tab)
- https://git.kernel.org/stable/c/6c22f86dd221eba0c7af645b1af73dcbc04ee27b (opens in a new tab)
- https://git.kernel.org/stable/c/331cd9461412e103d07595a10289de90004ac890 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-29988 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50379)Record last updated .