CVE-2026-97416btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 3, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 before 9f37a6d6ae9e998232e2ba091ab4999cdf967e1b; from a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 before e479236a8f4d85c4fb6b3f7c2556c21f583e2bf2; from a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 before 322f891b4d4fe64acb3351a0ffa62a7fa5ba7256; from a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 before 81a664ed8b1a44c76b204c4bd0d751317a02c5cd; from a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 before 9740dd0c17a4be8cc47a06c5ca5293471a7e286e; from a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 before 59f75e0c8724d4adebc08c7dd3ff2358b80c21f7; from a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7 before 18d32b0013efba19f7ad3e5b08d7aee813d604a6 | CNA record |
References
- https://git.kernel.org/stable/c/9f37a6d6ae9e998232e2ba091ab4999cdf967e1b
- https://git.kernel.org/stable/c/e479236a8f4d85c4fb6b3f7c2556c21f583e2bf2
- https://git.kernel.org/stable/c/322f891b4d4fe64acb3351a0ffa62a7fa5ba7256
- https://git.kernel.org/stable/c/81a664ed8b1a44c76b204c4bd0d751317a02c5cd
- https://git.kernel.org/stable/c/9740dd0c17a4be8cc47a06c5ca5293471a7e286e
- https://git.kernel.org/stable/c/59f75e0c8724d4adebc08c7dd3ff2358b80c21f7
- https://git.kernel.org/stable/c/18d32b0013efba19f7ad3e5b08d7aee813d604a6
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.