---
id: CVE-2026-97551
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  xfs: initialise args->total for parent pointer updates

  xfs_parent_da_args_init() builds an xfs_da_args from a zeroed
  xfs_parent_args (kmem_cache_zalloc), leaving args-…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  xfs: initialise args->total for parent pointer updates

  xfs_parent_da_args_init() builds an xfs_da_args from a zeroed
  xfs_parent_args (kmem_cache_zalloc), leaving args-…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= b7c62d90c12c6cc86f10b8a62cefe0029374b6ff <
    9ad85bce62cadfdf4242f6e6bbff2a52e51d30f1
  - >-
    Linux >= b7c62d90c12c6cc86f10b8a62cefe0029374b6ff <
    c66e138af626cad4210da449996ae9e07ee63add
  - >-
    Linux >= b7c62d90c12c6cc86f10b8a62cefe0029374b6ff <
    ac9032882d673dd6679e1d873a2dc0131a1aeb43
  - >-
    Linux >= b7c62d90c12c6cc86f10b8a62cefe0029374b6ff <
    8e4ebb6afaa34bd2e8ce52da231003d24111c2d6
  - Linux 6.10
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T11:17:05.530'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97551'
references:
  - url: 'https://git.kernel.org/stable/c/8e4ebb6afaa34bd2e8ce52da231003d24111c2d6'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/9ad85bce62cadfdf4242f6e6bbff2a52e51d30f1'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ac9032882d673dd6679e1d873a2dc0131a1aeb43'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c66e138af626cad4210da449996ae9e07ee63add'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-25T11:06:38.918Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

xfs: initialise args->total for parent pointer updates

xfs_parent_da_args_init() builds an xfs_da_args from a zeroed
xfs_parent_args (kmem_cache_zalloc), leaving args->total == 0.
xfs_da_grow_inode_int() treats that field as a running block reservation
and subtracts from it; because it is an xfs_extlen_t (uint32_t), the
first attr-fork growth wraps it to ~0U.  That defeats the free-space
check in xfs_alloc_space_available(), and when it coincides with an AG
that has exactly zero available blocks the allocation is clamped to
maxlen 0 and returns -ENOSPC, which xfs_defer_finish_noroll() escalates
to a filesystem shutdown.

Set args->total the way the log recovery path does
(xfs_attri_recover_work(), xfs_attr_item.c:706), in the add and replace
paths that can grow the fork.  Removals and lookups never grow it, so
they leave the field alone, matching that switch.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.