cveboard RSS feed

CVE-2026-97416

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

btrfs: balance: fix potential bg lookup failure in btrfs_may_alloc_data_chunk()

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7affectedgit9f37a6d6ae9e998232e2ba091ab4999cdf967e1bUnavailableNone listed
a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7affectedgite479236a8f4d85c4fb6b3f7c2556c21f583e2bf2UnavailableNone listed
a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7affectedgit322f891b4d4fe64acb3351a0ffa62a7fa5ba7256UnavailableNone listed
a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7affectedgit81a664ed8b1a44c76b204c4bd0d751317a02c5cdUnavailableNone listed
a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7affectedgit9740dd0c17a4be8cc47a06c5ca5293471a7e286eUnavailableNone listed
a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7affectedgit59f75e0c8724d4adebc08c7dd3ff2358b80c21f7UnavailableNone listed
a6f93c71d412ba8ed743152c3a54ad0b78dcd9c7affectedgit18d32b0013efba19f7ad3e5b08d7aee813d604a6UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
4.16affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver4.16UnavailableNone listed
5.10.271unaffectedsemverUnavailable5.10.*None listed
5.15.222unaffectedsemverUnavailable5.15.*None listed
6.1.189unaffectedsemverUnavailable6.1.*None listed
6.6.158unaffectedsemverUnavailable6.6.*None listed
6.12.111unaffectedsemverUnavailable6.12.*None listed
6.18.53unaffectedsemverUnavailable6.18.*None listed
7.2unaffectedoriginal_commit_for_fixUnavailable*None listed