PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-97416 Linux CVE debrief

A vulnerability in the Linux kernel's btrfs module can cause a null-pointer dereference when running btrfs balance due to metadata corruption. This issue arises when a chunk in the chunk tree lacks a corresponding block group in the in-memory cache, leading to a crash. The vulnerability is caused by a null-pointer dereference in the btrfs_may_alloc_data_chunk function. This occurs when a chunk item in the on-disk chunk tree does not have a matching block group item in the in-memory cache, resulting in a NULL return from btrfs_lookup_block_group(). The code currently only checks for this condition with an ASSERT statement, which does not prevent the crash. To fix this issue, a NULL

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-24
Original CVE updated
2026-09-25
Advisory published
2026-09-24
Advisory updated
2026-09-25

Who should care

Linux kernel developers and maintainers, as well as users of the btrfs file system, should be aware of this vulnerability and take steps to apply the provided patches. Linux kernel developers and users of the btrfs file system should apply patches to prevent potential DoS and data loss. This vulnerability can cause a kernel crash when running btrfs balance operations due to metadata corruption.

Why it matters

This vulnerability can cause a kernel crash when running btrfs balance operations due to metadata corruption. Linux kernel developers and users of the btrfs file system should apply patches to prevent potential DoS and data loss.

  • Denial of Service (DoS) due to kernel crash
  • Potential data loss or corruption if btrfs balance operations are interrupted

Technical summary

The vulnerability is caused by a null-pointer dereference in the btrfs_may_alloc_data_chunk function. This occurs when a chunk item in the on-disk chunk tree does not have a matching block group item in the in-memory cache, resulting in a NULL return from btrfs_lookup_block_group(). The code currently only checks for this condition with an ASSERT statement, which does not prevent the crash. To fix this issue, a NULL check has been added after btrfs_lookup_block_group() in btrfs_may_alloc_data_chunk(), and an error message is printed for clarity.

Defensive priority

Medium

Recommended defensive actions

  • Review and apply the provided patches to the Linux kernel's btrfs module.
  • Ensure that the system's Linux kernel is updated with the latest security patches.
  • Monitor the system's logs for any errors related to btrfs balance operations.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The vulnerability is caused by a null-pointer dereference in the btrfs_may_alloc_data_chunk function. This occurs when a chunk item in the on-disk chunk tree does not have a matching block group item in the in-memory cache, resulting in a NULL return from btrfs_lookup_block_group(). The code currently only checks for this condition with an ASSERT statement, which does not prevent the crash.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-97416 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-97416

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-97416 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97416

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/18d32b0013efba19f7ad3e5b08d7aee813d604a6

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/59f75e0c8724d4adebc08c7dd3ff2358b80c21f7

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/9740dd0c17a4be8cc47a06c5ca5293471a7e286e

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.