You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
btrfs
About this tag
The btrfs tag on WindowsForum.com covers the Btrfs (B-tree filesystem) as it appears in Linux kernel vulnerabilities, snapshot-based update rollback, and Microsoft's Azure Linux attestation. Discussions include CVEs such as CVE-2026-53284, CVE-2026-46129, CVE-2026-43118, CVE-2026-31519, CVE-2024-23850, CVE-2025-38260, and CVE-2024-46733, which detail bugs like transaction cleanup failures, double-free errors, truncate file reappearance after crash, broken subvolume dentries, subvolume race conditions, and qgroup reserve leaks. The tag also explores how Btrfs snapshots make Linux updates safe to roll back, contrasting with Windows recovery models. For WindowsForum readers, these threads highlight the relevance of Btrfs in mixed environments with Linux VMs, WSL, NAS, and containers.
Linus Torvalds released Linux 7.2-rc1 on Sunday, June 28, 2026, opening the public stabilization phase for the next mainline Linux kernel after two weeks of merge-window work following Linux 7.1. The release is not a finished kernel, and that distinction matters. What arrived this weekend is...
CVE-2026-53284 is a newly published Linux kernel vulnerability in Btrfs, disclosed in the NVD on June 26, 2026 and modified on June 28, that fixes a transaction writeback bug where dirty metadata tracking could be cleared after failed writes, leaving cleanup code unable to release dirty extent...
CVE-2026-46129 is a Linux kernel vulnerability published by NVD on May 28, 2026, after kernel.org reported a Btrfs double-free bug in the create_space_info() error path, where failed sysfs kobject setup can trigger cleanup of the same allocation twice. The flaw is narrow, technical, and...
CVE-2026-43118 is a Linux kernel Btrfs vulnerability published on May 6, 2026, in which log replay after a crash can restore a truncated file with its old non-zero size under a specific fsync, hardlink, or rename sequence. That sounds like a narrow filesystem corner case because it is one. But...
Background
A newly published Linux kernel CVE is drawing attention to a subtle but very real Btrfs failure mode: subvolumes can wind up with broken dentries, making them appear present to the VFS while behaving like dead entries underneath. In the reported scenario, ls shows a subvolume name in...
There is a reason so many Linux users stop flinching at the sight of an update prompt: filesystem snapshots turn software updates from a gamble into a reversible action. Instead of hoping a patch lands cleanly, the system can preserve a working state first and let you roll back in minutes if...
A recently disclosed robustness bug in the Linux kernel’s Btrfs implementation can trigger an assertion failure and a kernel crash when a newly created subvolume is read before the filesystem has finished the final steps of subvolume creation, producing a local-denial-of-service condition that...
Microsoft’s short MSRC line that “Azure Linux includes this open‑source library and is therefore potentially affected” is correct — but it is a product‑scoped attestation, not a universal guarantee that no other Microsoft product can contain the same vulnerable btrfs code. Treat Azure Linux as a...
Microsoft’s short advisory that “Azure Linux includes this open‑source library and is therefore potentially affected” is accurate — but it is a product‑scoped attestation, not a categorical guarantee that no other Microsoft product can carry the same vulnerable Btrfs code.
Background / Overview...
A race in btrfs's space bookkeeping has been fixed upstream after discovery of a non-atomic bitfield write in btrfs_clear_space_info_full that can leave the filesystem's reclaim infrastructure in a permanently inconsistent state — tracked as CVE-2025-68358.
Background
Btrfs is a modern...
Microsoft’s short advisory that “Azure Linux includes this open‑source library and is therefore potentially affected” is accurate — but it is a product‑scoped attestation, not a proof that no other Microsoft product or artifact could contain the same vulnerable btrfs code. The upstream CVE...
A recently assigned CVE—CVE-2025-40303—targets a corner case in the Linux kernel’s Btrfs implementation that can cause metadata writeback to proceed on a filesystem that has already been marked “in error,” leading to queueing of new work on workqueues that have been stopped and, in certain RAID...
A subtle but important memory-safety bug in the Linux kernel’s Btrfs file-handle encoder has been fixed upstream: CVE-2025-40205 closes an out‑of‑bounds write in btrfs_encode_fh that could, in specific circumstances, write eight bytes past the user-supplied buffer. This is primarily an...
A subtle race in Btrfs ordered-extent accounting can lead to a kernel panic: CVE-2024-58089 fixes a double‑accounting race in btrfs_run_delalloc_range that, when triggered on systems where block size (4K) is smaller than page size (64K) — commonly on certain aarch64 configurations — can...
A subtle race between Btrfs readahead and RAID stripe-tree lookups can trigger a kernel BUG that crashes systems performing block-group relocation — CVE-2024-49932 fixes this by skipping readahead of the relocation inode when the filesystem is backed by a RAID stripe tree, but operators must...
Microsoft’s short advisory that “Azure Linux includes this open‑source library and is therefore potentially affected” accurately describes the inventory Microsoft has completed — but it is a product‑scoped attestation, not a categorical statement that no other Microsoft product can include the...
Microsoft’s brief advisory that “Azure Linux includes this open‑source library and is therefore potentially affected” is accurate — but it is a product‑scoped attestation, not a categorical statement that no other Microsoft product can contain the same vulnerable Btrfs code. Background /...
Short answer (TL;DR)
No — Azure Linux is the only Microsoft product Microsoft has publicly attested (via its MSRC/VEX/CSAF work) to include the upstream btrfs code for CVE‑2025‑22115 so far, but that statement is a scoped inventory attestation, not a proof that no other Microsoft‑distributed...
Microsoft’s public notice that “Azure Linux includes this open‑source library and is therefore potentially affected” is accurate — and important — but it does not mean Azure Linux is the only Microsoft product that could contain the vulnerable Btrfs code. The Azure Linux attestation is a...
The Linux kernel bug tracked as CVE‑2024‑41067 — a Btrfs scrub path error that can trigger an ASSERT and host instability — has been publicly fixed upstream, and Microsoft’s published advisory names Azure Linux as a Microsoft‑branded product that includes the affected open‑source component and...