btrfs filesystem

CVE-2026-46160, published by NVD on May 28, 2026, describes a Linux kernel Btrfs bug in which directory removal failed to update last_unlink_trans, allowing a narrow fsync-and-crash sequence to produce failed log replay and an -EIO mount error. This is not a remote-code-execution fire drill, and...

CVE-2026-45934 is a Linux kernel Btrfs flaw disclosed by kernel.org and published by NVD on May 27, 2026, in which non-consecutive pending chunk allocations can make DUP chunk allocation overlap device extents and abort a filesystem transaction with EEXIST. The bug is not the sort of...

Btrfs has spent years living with a reputation that is equal parts innovation and caution: it is the Linux filesystem that promises copy-on-write flexibility, checksums, snapshots, and multi-device features, while also carrying the burden of every subtle accounting bug that can emerge when a...

The Linux kernel’s Btrfs filesystem has always lived at an interesting intersection of flexibility and fragility: it is a copy-on-write filesystem built for snapshots, checksumming, and online recovery, yet it must also behave sensibly when the filesystem is damaged, mounted read-only, or being...