CVE-2026-64567btrfs: reject free space cache with more entries than pages
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 17 days later
· 17 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 5b0e95bf607ddd59b39f52d3d55e6581c817b530 – < 8ded74c654a982dc8581a17b0caa7fcedb20de69
- affected 5b0e95bf607ddd59b39f52d3d55e6581c817b530 – < c9c38066b6446e83668c041702bb639b0ca49363
- affected 5b0e95bf607ddd59b39f52d3d55e6581c817b530 – < 094734c7aaa2b36751dc32480a680a4952685e78
- affected 5b0e95bf607ddd59b39f52d3d55e6581c817b530 – < 33878ba25e2638bc0c61623d7a05c9ca2b74c039
- affected 5b0e95bf607ddd59b39f52d3d55e6581c817b530 – < 404a0b986e0b6e79738fdf1f0ebbbc43b9acd2a2
- affected 5b0e95bf607ddd59b39f52d3d55e6581c817b530 – < 5e1b2ca6b34939e70fb0785e8222b53cf060016f
- affected 5b0e95bf607ddd59b39f52d3d55e6581c817b530 – < f9fef131fa3f59b857217f522fa5ea430d1b707c
- affected 5b0e95bf607ddd59b39f52d3d55e6581c817b530 – < a2d8d5647ed854e38f941741aea45b9eb15a6350
- affected 3.2
- unaffected < 3.2
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/8ded74c654a982dc8581a17b0caa7fcedb20de69 (opens in a new tab)
- https://git.kernel.org/stable/c/c9c38066b6446e83668c041702bb639b0ca49363 (opens in a new tab)
- https://git.kernel.org/stable/c/094734c7aaa2b36751dc32480a680a4952685e78 (opens in a new tab)
- https://git.kernel.org/stable/c/33878ba25e2638bc0c61623d7a05c9ca2b74c039 (opens in a new tab)
- https://git.kernel.org/stable/c/404a0b986e0b6e79738fdf1f0ebbbc43b9acd2a2 (opens in a new tab)
- https://git.kernel.org/stable/c/5e1b2ca6b34939e70fb0785e8222b53cf060016f (opens in a new tab)
- https://git.kernel.org/stable/c/f9fef131fa3f59b857217f522fa5ea430d1b707c (opens in a new tab)
- https://git.kernel.org/stable/c/a2d8d5647ed854e38f941741aea45b9eb15a6350 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-53261 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64567)Record last updated .