btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk() [BUG] Running btrfs balance can trigger a null-ptr-deref before relocating a data chunk when metadata corruption leaves a chunk in the chunk tree without a corresponding block group in the in-memory cache: KASAN: null-ptr-deref in range [0x0000000000000088-0x000000000000008f] RIP: 0010:btrfs_may_alloc_data_chunk+0x40/0x1c0 fs/btrfs/volumes.c:3601 Call Trace: __btrfs_balance fs/btrfs/volumes.c:4217 [inline] btrfs_balance+0x2516/0x42b0 fs/btrfs/volumes.c:4604 btrfs_ioctl_balance fs/btrfs/ioctl.c:3577 [inline] btrfs_ioctl+0x25cf/0x5b90 fs/btrfs/ioctl.c:5313 ... [CAUSE] __btrfs_balance() iterates the on-disk chunk tree and passes the chunk logical bytenr to btrfs_may_alloc_data_chunk() before relocating a data chunk. That helper then queries the in-memory block group cache: cache = btrfs_lookup_block_group(fs_info, chunk_offset); chunk_type = cache->flags; /* cache may be NULL */ A corrupt image can contain a chunk item whose matching block group item is missing, so no block group is ever inserted into the cache. In that case btrfs_lookup_block_group() returns NULL. The code only guards this with ASSERT(cache), which becomes a no-op when CONFIG_BTRFS_ASSERT is disabled. The subsequent dereference of cache->flags therefore crashes the kernel. [FIX] Add a NULL check after btrfs_lookup_block_group() in btrfs_may_alloc_data_chunk() and print and error message for clarity.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 · fixed in 9f37a6d6ae9e998232e2ba091ab4999cdf967e1b; From a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 · fixed in e479236a8f4d85c4fb6b3f7c2556c21f583e2bf2; From a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 · fixed in 322f891b4d4fe64acb3351a0ffa62a7fa5ba7256; From a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 · fixed in 81a664ed8b1a44c76b204c4bd0d751317a02c5cd; From a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 · fixed in 9740dd0c17a4be8cc47a06c5ca5293471a7e286e; From a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 · fixed in 59f75e0c8724d4adebc08c7dd3ff2358b80c21f7; From a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 · fixed in 18d32b0013efba19f7ad3e5b08d7aee813d604a6
- Linux Linux
4.16
- KernelLinux
From 4.16.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53
References 7
git.kernel.org
- stable/c/9f37a6d6ae9e998232e2ba091ab4999cdf967e1b
- stable/c/e479236a8f4d85c4fb6b3f7c2556c21f583e2bf2
- stable/c/322f891b4d4fe64acb3351a0ffa62a7fa5ba7256
- stable/c/81a664ed8b1a44c76b204c4bd0d751317a02c5cd
- stable/c/9740dd0c17a4be8cc47a06c5ca5293471a7e286e
- stable/c/59f75e0c8724d4adebc08c7dd3ff2358b80c21f7
- stable/c/18d32b0013efba19f7ad3e5b08d7aee813d604a6