xfs: initialise args->total for parent pointer updates
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.111, 6.18.53, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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->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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b7c62d90c12c6cc86f10b8a62cefe0029374b6ff · fixed in 9ad85bce62cadfdf4242f6e6bbff2a52e51d30f1; From b7c62d90c12c6cc86f10b8a62cefe0029374b6ff · fixed in c66e138af626cad4210da449996ae9e07ee63add; From b7c62d90c12c6cc86f10b8a62cefe0029374b6ff · fixed in ac9032882d673dd6679e1d873a2dc0131a1aeb43; From b7c62d90c12c6cc86f10b8a62cefe0029374b6ff · fixed in 8e4ebb6afaa34bd2e8ce52da231003d24111c2d6
- Linux Linux
6.10
- KernelLinux
From 6.10.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7