CVEvulnerability

CVE-2026-53050

7.8 HIGH Published 2026-06-24 Modified 2026-10-15 Official page ↗
Status
Modified
Published
2026-06-24
Last modified
2026-10-15
Assigner
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-362

Description

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.

Affected configurations

• linux linux kernel (>= 4.19.297 < 4.20) • linux linux kernel (>= 5.4.259 < 5.5) • linux linux kernel (>= 5.10.199 < 5.10.258) • linux linux kernel (>= 5.15.136 < 5.15.209) • linux linux kernel (>= 6.1.59 < 6.1.175) • linux linux kernel (>= 6.5.8 < 6.6) • linux linux kernel (>= 6.6.1 < 6.6.141) • linux linux kernel (>= 6.7 < 6.12.91) • linux linux kernel (>= 6.13 < 6.18.33) • linux linux kernel (>= 6.19 < 7.0.10) • linux linux kernel 6.6

Related

Weakness · CWE (1)

  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness

References