Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
quota: Fix race of dquot_scan_active() with quota deactivation
In the Linux kernel, the following vulnerability has been resolved: quota: Fix race of dquot_scan_active() with quota deactivation dquot_scan_active() can race with quota deactivation in quota_release_workfn() like: CPU0 (quota_release_workfn) CPU1 (dquot_scan_active) ============================== ============================== spin_lock(&dq_list_lock); list_replace_init( &releasing_dquots, &rls_head); /* dquot X on rls_head, dq_count == 0, DQ_ACTIVE_B still set */ spin_unlock(&dq_list_lock); synchronize_srcu(&dquot_srcu); spin_lock(&dq_list_lock); list_for_each_entry(dquot, &inuse_list, dq_inuse) { /* finds dquot X */ dquot_active(X) -> true atomic_inc(&X->dq_count); } spin_unlock(&dq_list_lock); spin_lock(&dq_list_lock); dquot = list_first_entry(&rls_head); WARN_ON_ONCE(atomic_read(&dquot->dq_count)); The problem is not only a cosmetic one as under memory pressure the caller of dquot_scan_active() can end up working on freed dquot. Fix the problem by making sure the dquot is removed from releasing list when we acquire a reference to it.
References
Affected products
- =<6.18.*
- <5.15.209
- =<7.0.*
- <e93ab401da4b2e2c1b8ef2424de2f238d51c8b2d
- <5.10.258
- <fdd424d7c35633ac577fd87d1b043d1b8a6cd350
- =<6.1.*
- <6.6
- ==2a1ddddba6541143c8f73962f3021f1789114284
- <4.20
- <61e25f664dc2a08299e07d84c85776abc2350f75
- <6678dde265708003c2b42551af4a2e3cb05decd5
- ==bb7e3a019b52d829949d02b64ebab37838148fbf
- <6.6
- <6.1.175
- <5.5
- ==6.6
- ==061a18239ced5eb086967a2b4451cb1cc5ce0702
- <ac8a2e0d287ebf35e5d7e51e260b4e146648ba4a
- <2bdc80f4619411e5bd4a3ef23f51e14021ed457c
- =<5.15.*
- <82cbdb4c1ebb5ea7d7bd45c18d3483b5bd32ebc1
- <f9438cb8c8ec3adc84b2b450a3aab0123d074c3b
- =<*
- =<6.12.*
- =<5.10.*
- =<6.6.*