btrfs: fix re-dirty process of tree-log nodes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix re-dirty process of tree-log nodes
There is a report of a transaction abort of -EAGAIN with the following script.
#!/bin/sh
for d in sda sdb; do mkfs.btrfs -d single -m single -f /dev/\${d} done
mount /dev/sda /mnt/test mount /dev/sdb /mnt/scratch
for dir in test scratch; do echo 3 >/proc/sys/vm/drop_caches fio --directory=/mnt/\${dir} --name=fio.\${dir} --rw=read --size=50G --bs=64m \ --numjobs=$(nproc) --time_based --ramp_time=5 --runtime=480 \ --group_reporting |& tee /dev/shm/fio.\${dir} echo 3 >/proc/sys/vm/drop_caches done
for d in sda sdb; do umount /dev/\${d} done
From the CVE record · Linux
The Linux kernel has a flaw in how btrfs tree-log nodes are re-dirtied. Under the reported local filesystem workload, it can abort a transaction and force the filesystem read-only. The input does not establish an authentication requirement or a network attack path.
Engineers running Linux kernels with btrfs should check their kernel versions; the affected version range is not specified.