xfs: restore nofs context unconditionally in xfs_trans_roll
- 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 7.1.11, 7.2.1
- 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: restore nofs context unconditionally in xfs_trans_roll When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context is cleared but only restored in the success path. This leaves the error path without nofs protection, causing a circular lock dependency between xfs_nondir_ilock_class and fs_reclaim: CPU0 CPU1 ---- ---- lock(&xfs_nondir_ilock_class); lock(fs_reclaim); lock(&xfs_nondir_ilock_class); lock(fs_reclaim); Fix this by moving xfs_trans_set_context() before the error check so that nofs context is always restored on the new transaction.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From a1ca658d649a4d8972e2e21ac2625b633217e327 · fixed in b09198cf90ccf296970b774beea1c1ddb260f94c; From a1ca658d649a4d8972e2e21ac2625b633217e327 · fixed in 4d00a39c676274f4071b467e630565ac1e3ae0f2; From a1ca658d649a4d8972e2e21ac2625b633217e327 · fixed in 0241ea5fb0fe86d2a673163b2f5815111aadc7f7
- Linux Linux
7.0
- KernelLinux
From 7.0.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1