CVE-2025-68358
- Source
- https://cve.org/CVERecord?id=CVE-2025-68358
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68358.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2025-68358
- Downstream
- Published
- 2025-12-24T10:32:47.692Z
- Modified
- 2026-02-19T21:04:54.665542Z
- Summary
- btrfs: fix racy bitfield write in btrfs_clear_space_info_full()
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix racy bitfield write in btrfsclearspaceinfofull()
From the memory-barriers.txt document regarding memory barrier ordering guarantees:
(*) These guarantees do not apply to bitfields, because compilers often generate code to modify these using non-atomic read-modify-write sequences. Do not attempt to use bitfields to synchronize parallel algorithms.
(*) Even in cases where bitfields are protected by locks, all fields in a given bitfield must be protected by one lock. If two fields in a given bitfield are protected by different locks, the compiler's non-atomic read-modify-write sequences can cause an update to one field to corrupt the value of an adjacent field.
btrfsspaceinfo has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush:
struct btrfsspaceinfo { struct btrfsfsinfo * fsinfo; /* 0 8 */ struct btrfsspaceinfo * parent; /* 8 8 */ ... int clamp; /* 172 4 */ unsigned int full:1; /* 176: 0 4 */ unsigned int chunkalloc:1; /* 176: 1 4 / unsigned int flush:1; / 176: 2 4 */ ...
Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield members protected by a lock, all writes to all the bitfields must use the lock. They almost universally do, except for btrfsclearspaceinfofull() which iterates over the space_infos and writes out found->full = 0 without a lock.
Imagine that we have one thread completing a transaction in which we finished deleting a blockgroup and are thus calling btrfsclearspaceinfofull() while simultaneously the data reclaim ticket infrastructure is running doasyncreclaimdata_space():
T1 T2btrfscommittransaction btrfsclearspaceinfofull datasinfo->full = 0 READ: full:0, chunkalloc:0, flush:1 doasyncreclaimdataspace(datasinfo) spinlock(&spaceinfo->lock); if(listempty(tickets)) spaceinfo->flush = 0; READ: full: 0, chunkalloc:0, flush:1 MOD/WRITE: full: 0, chunkalloc:0, flush:0 spinunlock(&spaceinfo->lock); return; MOD/WRITE: full:0, chunkalloc:0, flush:1
and now datasinfo->flush is 1 but the reclaim worker has exited. This breaks the invariant that flush is 0 iff there is no work queued or running. Once this invariant is violated, future allocations that go into _reservebytes() will add tickets to spaceinfo->tickets but will see space_info->flush is set to 1 and not queue the work. After this, they will block forever on the resulting ticket, as it is now impossible to kick the worker again.
I also confirmed by looking at the assembly of the affected kernel that it is doing RMW operations. For example, to set the flush (3rd) bit to 0, the assembly is: andb $0xfb,0x60(%rbx) and similarly for setting the full (1st) bit to 0: andb $0xfe,-0x20(%rax)
So I think this is really a bug on practical systems. I have observed a number of systems in this exact state, but am currently unable to reproduce it.
Rather than leaving this footgun lying around for the future, take advantage of the fact that there is room in the struct anyway, and that it is already quite large and simply change the three bitfield members to bools. This avoids writes to space_info->full having any effect on ---truncated---
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68358.json" }- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/38e818718c5e04961eea0fa8feff3f100ce40408
- https://git.kernel.org/stable/c/55835646da78e83e7ad06abd741ca8fd8c0b0ea7
- https://git.kernel.org/stable/c/6f442808a86eef847ee10afa9e6459494ed85bb3
- https://git.kernel.org/stable/c/742b90eaf394f0018352c0e10dc89763b2dd5267
- https://git.kernel.org/stable/c/b0bb67385480a3aa4c54b139e4f371ddd06b5150
- https://git.kernel.org/stable/c/d4a81b8ec639895999275ea2472c69825cd67ea4
- https://git.kernel.org/stable/c/db4ae18e1b31e0421fb5312e56aefa382bbc6ece
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68358.json
- https://nvd.nist.gov/vuln/detail/CVE-2025-68358
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced957780eb2788d8c218d539e19a85653f51a96dc1Fixedb0bb67385480a3aa4c54b139e4f371ddd06b5150Fixed55835646da78e83e7ad06abd741ca8fd8c0b0ea7Fixedd4a81b8ec639895999275ea2472c69825cd67ea4Fixeddb4ae18e1b31e0421fb5312e56aefa382bbc6eceFixed6f442808a86eef847ee10afa9e6459494ed85bb3Fixed742b90eaf394f0018352c0e10dc89763b2dd5267Fixed38e818718c5e04961eea0fa8feff3f100ce40408
Affected versions
v4.*
v5.*
v6.*
Linux / Kernel
Package
- Name
- Kernel
Affected ranges
- Type
- ECOSYSTEM
- Events
-
Introduced4.8.0Fixed5.15.201
- Type
- ECOSYSTEM
- Events
-
Introduced5.16.0Fixed6.1.164
- Type
- ECOSYSTEM
- Events
-
Introduced6.2.0Fixed6.6.124
- Type
- ECOSYSTEM
- Events
-
Introduced6.7.0Fixed6.12.68
- Type
- ECOSYSTEM
- Events
-
Introduced6.13.0Fixed6.17.13
- Type
- ECOSYSTEM
- Events
-
Introduced6.18.0Fixed6.18.2