Kernel crash via dangling Btrfs quota pointer
Published Sep 18, 2025 · Updated Sep 18, 2025
Use-after-free in the Btrfs quota code in affected Linux kernels allows local users to crash the kernel through concurrent quota ioctls. During btrfs_quota_enable(), an in-progress qgroup rescan makes qgroup_rescan_init() return -EINPROGRESS; the error path frees the quota root but leaves fs_info->quota_root pointing to the freed object. Reachability requires a Btrfs filesystem and local access able to race quota enablement against a quota-rescan ioctl, with the resulting dangling pointer threatening kernel availability.
Summary
What happened
Use-after-free in the Btrfs quota code in affected Linux kernels allows local users to crash the kernel through concurrent quota ioctls. During btrfs_quota_enable(), an in-progress qgroup rescan makes qgroup_rescan_init() return -EINPROGRESS; the error path frees the quota root but leaves fs_info->quota_root pointing to the freed object. Reachability requires a Btrfs filesystem and local access able to race quota enablement against a quota-rescan ioctl, with the resulting dangling pointer threatening kernel availability.
The record
- CVE
- CVE-2022-50379
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0efd9dfc00d677a1d0929319a6103cb2dfc41c22
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <26b7c0ac49a3eea15559c9d84863736a6d1164b4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <331cd9461412e103d07595a10289de90004ac890
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47b5ffe86332af95f0f52be0a63d4da7c2b37b55
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4b996a3014ef014af8f97b60c35f5289210a4720
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6c22f86dd221eba0c7af645b1af73dcbc04ee27b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c97f6d528c3f1c83a6b792a8a7928c236c80b8fe
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo