xfs: initialise error in xfs_defer_finish_one()
- 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 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3f3cec031099c37513727efc978a12b6346e326d · fixed in 30748a24b9f04f9a83599ba907cc8fbff0729f3c; From 3f3cec031099c37513727efc978a12b6346e326d · fixed in ba949a14446b7346e92e676ee3fe2bb79d9ce450; From 3f3cec031099c37513727efc978a12b6346e326d · fixed in 6b507c239884f7d4bf8339f6e9eb8bfcb540afde; From 3f3cec031099c37513727efc978a12b6346e326d · fixed in 6176d21d7bd609632c5b7e87a3adb9be29ec1e72
- Linux Linux
6.8
- KernelLinux
From 6.8.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7