CVE-2026-98448

What it actually does

Failure to release an igrab'd inode reference on the XFS orphanage directory when a chown operation fails, causing a kernel resource leak.

Why it matters to the business

On XFS filesystems, repeated failed chown operations on certain inodes can gradually exhaust kernel memory, leading to performance degradation or system instability over long periods.

How an attack unfolds

An attacker would need to trigger repeated chown failures against the orphanage directory inode in XFS; the leak itself provides no direct code execution path and is not known to be exploited by any threat actors.

How to fix it

Update the Linux kernel to a version containing the fix that releases the orphanage directory inode reference on chown failure.

How to confirm the fix worked

Confirm the kernel version includes the commit that adds the missing iput call for the orphanage directory inode on chown error paths; review XFS source for the corrected reference handling.

Typical attack path

1. Identify XFS filesystem usage on target host
2. Trigger chown operations that fail on files involving the orphanage directory
3. Repeat to accumulate leaked inode references
4. Observe gradual kernel memory pressure or resource exhaustion

How to detect it

Review kernel logs for XFS inode reference warnings or memory allocation patterns; no specific post-exploitation artifacts are known due to the nature of the leak.

What your security team should do

• Prioritize kernel updates for systems running XFS filesystems
• Monitor kernel memory usage on XFS hosts for unexpected growth
• Apply available distro kernel packages as soon as released