btrfs: qgroup: fix race between quota disable and quota rescan ioctl
In the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix race between quota disable and quota rescan ioctl There's a race between a task disabling quotas and another running the rescan ioctl that can result in a use-after-free of qgroup records from the fs_info->qgroup_tree rbtree. This happens as follows: 1) Task A enters btrfs_ioctl_quota_rescan() -> btrfs_qgroup_rescan(); 2) Task B enters btrfs_quota_disable() and calls btrfs_qgroup_wait_for_completion(), which does nothing because at that point fs_info->qgroup_rescan_running is false (it wasn't set yet by task A); 3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups from fs_info->qgroup_tree without taking the lock fs_info->qgroup_lock; 4) Task A enters qgroup_rescan_zero_tracking() which starts iterating the fs_info->qgroup_tree tree while holding fs_info->qgroup_lock, but task B is freeing qgroup records from that tree without holding the lock, resulting in a use-after-free. Fix this by taking fs_info->qgroup_lock at btrfs_free_qgroup_config(). Also at btrfs_qgroup_rescan() don't start the rescan worker if quotas were already disabled.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.149, 6.12.44, 6.15.11, 6.16.2, 6.6.103
- CVEs
- CVE-2025-39759
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 04:28 UTC · Revision 1
Source evidence
btrfs: qgroup: fix race between quota disable and quota rescan ioctl
core-osv · Original sourcePublished 11 Sept 2025, 16:52 UTC
In the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix race between quota disable and quota rescan ioctl There's a race between a task disabling quotas and another running the rescan ioctl that can result in a use-after-free of qgroup records from the fs_info->qgroup_tree rbtree. This happens as follows: 1) Task A enters btrfs_ioctl_quota_rescan() -> btrfs_qgroup_rescan(); 2) Task B enters btrfs_quota_disable() and calls btrfs_qgroup_wait_for_completion(), which does nothing because at that point fs_info->qgroup_rescan_running is false (it wasn't set yet by task A); 3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups from fs_info->qgroup_tree without taking the lock fs_info->qgroup_lock; 4) Task A enters qgroup_rescan_zero_tracking() which starts iterating the fs_info->qgroup_tree tree while holding fs_info->qgroup_lock, but task B is freeing qgroup records from that tree without holding the lock, resulting in a use-after-free. Fix this by taking fs_info->qgroup_lock at btrfs_free_qgroup_config(). Also at btrfs_qgroup_rescan() don't start the rescan worker if quotas were already disabled.
osv:CVE-2025-39759
Kernel
Fixed versions: 6.1.149, 6.6.103, 6.12.44, 6.15.11, 6.16.2
Complete source record
{
"id": "1f49dbb1af9977cfa8b75bc70f81e4b9c71d99b04873d989eec3a91acc85022e",
"url": "https://osv.dev/vulnerability/CVE-2025-39759",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "btrfs: qgroup: fix race between quota disable and quota rescan ioctl",
"summary": "In the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix race between quota disable and quota rescan ioctl There's a race between a task disabling quotas and another running the rescan ioctl that can result in a use-after-free of qgroup records from the fs_info->qgroup_tree rbtree. This happens as follows: 1) Task A enters btrfs_ioctl_quota_rescan() -> btrfs_qgroup_rescan(); 2) Task B enters btrfs_quota_disable() and calls btrfs_qgroup_wait_for_completion(), which does nothing because at that point fs_info->qgroup_rescan_running is false (it wasn't set yet by task A); 3) Task B calls btrfs_free_qgroup_config() which starts freeing qgroups from fs_info->qgroup_tree without taking the lock fs_info->qgroup_lock; 4) Task A enters qgroup_rescan_zero_tracking() which starts iterating the fs_info->qgroup_tree tree while holding fs_info->qgroup_lock, but task B is freeing qgroup records from that tree without holding the lock, resulting in a use-after-free. Fix this by taking fs_info->qgroup_lock at btrfs_free_qgroup_config(). Also at btrfs_qgroup_rescan() don't start the rescan worker if quotas were already disabled.",
"evidence": "osv:CVE-2025-39759",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.149",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.103",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.44",
"evidence": "/affected/1/ranges"
},
{
"value": "6.15.11",
"evidence": "/affected/1/ranges"
},
{
"value": "6.16.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-39759",
"aliases": [
"CVE-2025-39759"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "e685da14af6b31e4b336a110cb1bae1afc268be8"
},
{
"fixed": "7cda0fdde5d9890976861421d207870500f9aace"
},
{
"fixed": "b172535ccba12f0cf7d23b3b840989de47fc104d"
},
{
"fixed": "dd0b28d877b293b1d7f8727a7de08ae36b6b9ef0"
},
{
"fixed": "c38028ce0d0045ca600b6a8345a0ff92bfb47b66"
},
{
"fixed": "2fd0f5ceb997f90f4332ccbab6c7e907e6b2d0eb"
},
{
"fixed": "e1249667750399a48cafcf5945761d39fa584edf"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39759.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.12.0"
},
{
"fixed": "6.1.149"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.103"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.44"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.15.11"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.16.0"
},
{
"fixed": "6.16.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-39759.json"
}
}
],
"modified": "2026-10-28T02:30:49.687898275Z",
"provider": "osv",
"references": [
"https://cert-portal.siemens.com/productcert/html/ssa-032379.html",
"https://git.kernel.org/stable/c/2fd0f5ceb997f90f4332ccbab6c7e907e6b2d0eb",
"https://git.kernel.org/stable/c/7cda0fdde5d9890976861421d207870500f9aace",
"https://git.kernel.org/stable/c/b172535ccba12f0cf7d23b3b840989de47fc104d",
"https://git.kernel.org/stable/c/c38028ce0d0045ca600b6a8345a0ff92bfb47b66",
"https://git.kernel.org/stable/c/dd0b28d877b293b1d7f8727a7de08ae36b6b9ef0",
"https://git.kernel.org/stable/c/e1249667750399a48cafcf5945761d39fa584edf",
"https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39759.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-39759",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/39xxx/CVE-2025-39759.json"
}
},
"related_cves": [
{
"value": "CVE-2025-39759",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 518132,
"published_at": "2025-09-11T16:52:28.314+00:00"
}