The vulnerability in the Linux kernel's __filemap_add_folio() function involved improper handling of the xas.xa_index during retries in the split-a-conflict loop. When a new node allocation failed with GFP_NOWAIT, the function dropped the lock and retried after allocation. However, if another thread resolved the conflict in the meantime by inserting a folio at the same index, the retry could incorrectly insert the folio at a rounded-down intermediate index. This led to memory corruption detected by !folio_contains() checks and caused rare SIGILL and SIGSEGV crashes. The patch restores the original xas.xa_index before retrying, ensuring the index is re-evaluated and preventing incorrect insertion.

The vulnerability could cause memory corruption in the kernel's page cache management, leading to rare crashes such as illegal instruction (SIGILL) and segmentation faults (SIGSEGV). It also caused executable code pages to be misplaced in memory. This could affect system stability and reliability but no known exploits in the wild have been reported.

A patch has been applied to the Linux kernel to fix this issue by restoring the original index before retrying the insertion. Users should update to the fixed kernel version containing this patch. Since this is a kernel-level fix, upgrading the kernel is the recommended remediation. No further mitigation steps are indicated.