Skip to main content
VulnerabilityPublished Updated

CVE-2026-97551: Linux kernel · xfs: initialise args->total for parent pointer updates

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in c66e138af626cad4210da449996ae9e07ee63add : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in c66e138af626cad4210da449996ae9e07ee63add, ac9032882d673dd6679e1d873a2dc0131a1aeb43, 9ad85bce62cadfdf4242f6e6bbff2a52e51d30f1 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to c66e138af626cad4210da449996ae9e07ee63add, ac9032882d673dd6679e1d873a2dc0131a1aeb43, 9ad85bce62cadfdf4242f6e6bbff2a52e51d30f1 or 8e4ebb6afaa34bd2e8ce52da231003d24111c2d6.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b7c62d90c12c6cc86f10b8a62cefe0029374b6ff, < c66e138af626cad4210da449996ae9e07ee63add
Fixed in
  • c66e138af626cad4210da449996ae9e07ee63add
LinuxLinuxAffected
  • ≥ b7c62d90c12c6cc86f10b8a62cefe0029374b6ff, < ac9032882d673dd6679e1d873a2dc0131a1aeb43
Fixed in
  • ac9032882d673dd6679e1d873a2dc0131a1aeb43
LinuxLinuxAffected
  • ≥ b7c62d90c12c6cc86f10b8a62cefe0029374b6ff, < 9ad85bce62cadfdf4242f6e6bbff2a52e51d30f1
Fixed in
  • 9ad85bce62cadfdf4242f6e6bbff2a52e51d30f1
LinuxLinuxAffected
  • ≥ b7c62d90c12c6cc86f10b8a62cefe0029374b6ff, < 8e4ebb6afaa34bd2e8ce52da231003d24111c2d6
Fixed in
  • 8e4ebb6afaa34bd2e8ce52da231003d24111c2d6
LinuxLinuxAffected
  • =6.10
Fixed in–

Description

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.

References

Community reviews

Loading reviews…