xfs: restore nofs context unconditionally in xfs_trans_roll
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0241ea5fb0fe86d2a673163b2f5815111aadc7f7, Kernel 4d00a39c676274f4071b467e630565ac1e3ae0f2 and Kernel b09198cf90ccf296970b774beea1c1ddb260f94c.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=a1ca658d649a4d8972e2e21ac2625b633217e327 <0241ea5fb0fe86d2a673163b2f5815111aadc7f7, >=a1ca658d649a4d8972e2e21ac2625b633217e327 <4d00a39c676274f4071b467e630565ac1e3ae0f2, >=a1ca658d649a4d8972e2e21ac2625b633217e327 <b09198cf90ccf296970b774beea1c1ddb260f94c | 0241ea5fb0fe86d2a673163b2f5815111aadc7f7, 4d00a39c676274f4071b467e630565ac1e3ae0f2, b09198cf90ccf296970b774beea1c1ddb260f94c |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket