CVE-2025-37856
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.12.24
- Linux Kernel < 6.13.12
- Linux Kernel < 6.14.3
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-37856.md and follow it. Check whether this project is affected by CVE-2025-37856. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/185fd73e5ac06027c4be9a129e59193f6a3ef202
- https://git.kernel.org/stable/c/7511e29cf1355b2c47d0effb39e463119913e2f6
- https://git.kernel.org/stable/c/909e60fb469d4101c6b08cf6e622efb062bb24a1
- https://git.kernel.org/stable/c/bf089c4d1141b27332c092b1dcca5022c415a3b6
References
- https://git.kernel.org/stable/c/185fd73e5ac06027c4be9a129e59193f6a3ef202
- https://git.kernel.org/stable/c/7511e29cf1355b2c47d0effb39e463119913e2f6
- https://git.kernel.org/stable/c/9039afe6240ae01d6caf2fa731590ac74fb8a69b
- https://git.kernel.org/stable/c/909e60fb469d4101c6b08cf6e622efb062bb24a1
- https://git.kernel.org/stable/c/bf089c4d1141b27332c092b1dcca5022c415a3b6
- https://git.kernel.org/stable/c/ccb20413e7c82e4429c81f10d0e36cd9c0c643cd