quota: flush quota_release_work upon quota writeback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ dabc8b20756601b9e1cc85a81d47d3f98ed4d13a · < 8ea87e34792258825d290f4dc5216276e91cb224| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
quota: flush quota_release_work upon quota writeback
One of the paths quota writeback is called from is:
freeze_super() sync_filesystem() ext4_sync_fs() dquot_writeback_dquots()
Since we currently don't always flush the quota_release_work queue in this path, we can end up with the following race:
1. dquot are added to releasing_dquots list during regular operations. 2. FS Freeze starts, however, this does not flush the quota_release_work queue. 3. Freeze completes. 4. Kernel eventually tries to flush the workqueue while FS is frozen which hits a WARN_ON since transaction gets started during frozen state:
ext4_journal_check_start+0x28/0x110 [ext4] (unreliable) __ext4_journal_start_sb+0x64/0x1c0 [ext4] ext4_release_dquot+0x90/0x1d0 [ext4] quota_release_workfn+0x43c/0x4d0
Which is the following line:
From the CVE record · Linux
A race between quota release work and filesystem freeze can cause the Linux kernel to start an ext4 transaction after the filesystem is frozen, triggering a warning. The reported impact is dmesg noise that can cause generic/390 to fail. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running the Linux kernel with ext4 and quota writeback should check their systems; affected versions are not specified.