xfs: initialise error in xfs_defer_finish_one()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xfs: initialise error in xfs_defer_finish_one()
xfs_defer_finish_one() declares error without an initialiser and only assigns it inside the loop over dfp->dfp_work. When that list is empty the loop body never runs, control falls through to the "Done with the dfp, free it" path, and the function returns an indeterminate value.
An item-less pending item reaches this through xfs_defer_add_barrier(), which xfs_reap_ag_blocks() uses on any CONFIG_XFS_ONLINE_REPAIR kernel. xfs_defer_finish_noroll() treats any non-EAGAIN return as fatal, so a non-zero stack value turns a successful barrier into a SHUTDOWN_CORRUPT_INCORE in the middle of a repair. Zero is the correct result: reaching the free path means the item loop drained without a non-zero error.
From the CVE record · Linux
An uninitialized return value in xfs_defer_finish_one() can cause a successful XFS repair barrier to be treated as a fatal error, triggering SHUTDOWN_CORRUPT_INCORE during online repair. This can occur on kernels with CONFIG_XFS_ONLINE_REPAIR enabled; the input does not describe an attacker path, authentication requirement, or user interaction.
Operators running Linux kernels with CONFIG_XFS_ONLINE_REPAIR enabled should check whether their kernel includes the fix; affected versions were not specified.