CVE-2025-37856btrfs: harden block_group::bg_list against list_del() races
- 7.8HighCVSS base score
- 0.31%Exploitation in 30 daysEPSS · top 76% 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: harden block_group::bg_list against list_del() races As far as I can tell, these calls of list_del_init() on bg_list cannot run concurrently with btrfs_mark_bg_unused() or btrfs_mark_bg_to_reclaim(), as they are in transaction error paths and situations where the block group is readonly. However, if there is any chance at all of racing with mark_bg_unused(), or a different future user of bg_list, better to be safe than sorry. Otherwise we risk the following interleaving (bg_list refcount in parens) T1 (some random op) T2 (btrfs_mark_bg_unused) !list_empty(&bg->bg_list); (1) list_del_init(&bg->bg_list); (1) list_move_tail (1) btrfs_put_block_group (0) btrfs_delete_unused_bgs bg = list_first_entry list_del_init(&bg->bg_list); btrfs_put_block_group(bg); (-1) Ultimately, this results in a broken ref count that hits zero one deref early and the real final deref underflows the refcount, resulting in a WARNING.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 18 months later
· 18 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 |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.31% · top 76% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 01eca70ef8cf499d0cb6d1bbd691558e7792cf17 – < ccb20413e7c82e4429c81f10d0e36cd9c0c643cd
- affected a9f189716cf15913c453299d72f69c51a9b0f86b – < 9039afe6240ae01d6caf2fa731590ac74fb8a69b
- affected a9f189716cf15913c453299d72f69c51a9b0f86b – < bf089c4d1141b27332c092b1dcca5022c415a3b6
- affected a9f189716cf15913c453299d72f69c51a9b0f86b – < 909e60fb469d4101c6b08cf6e622efb062bb24a1
- affected a9f189716cf15913c453299d72f69c51a9b0f86b – < 185fd73e5ac06027c4be9a129e59193f6a3ef202
- affected a9f189716cf15913c453299d72f69c51a9b0f86b – < 7511e29cf1355b2c47d0effb39e463119913e2f6
- affected edf3b5aadb2515c808200b904baa5b70a727f0ac
- affected 5d19abcffd8404078dfa7d7118cec357b5e7bc58
- affected 6.1.47 – < 6.1.191
- affected 5.15.128 – < 5.16
- affected 6.4.12 – < 6.5
- affected 6.5
- unaffected < 6.5
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.24 – ≤ 6.12.*
- unaffected 6.13.12 – ≤ 6.13.*
- unaffected 6.14.3 – ≤ 6.14.*
- unaffected 6.15 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ccb20413e7c82e4429c81f10d0e36cd9c0c643cd (opens in a new tab)
- https://git.kernel.org/stable/c/9039afe6240ae01d6caf2fa731590ac74fb8a69b (opens in a new tab)
- https://git.kernel.org/stable/c/bf089c4d1141b27332c092b1dcca5022c415a3b6 (opens in a new tab)
- https://git.kernel.org/stable/c/909e60fb469d4101c6b08cf6e622efb062bb24a1 (opens in a new tab)
- https://git.kernel.org/stable/c/185fd73e5ac06027c4be9a129e59193f6a3ef202 (opens in a new tab)
- https://git.kernel.org/stable/c/7511e29cf1355b2c47d0effb39e463119913e2f6 (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-14136 (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-2025-37856)Record last updated .