CVE-2026-53050

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
2.9%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

quota: Fix race of dquot_scan_active() with quota deactivation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fdd424d7c35633ac577fd87d1b043d1b8a6cd350
generic

quota: Fix race of dquot_scan_active() with quota deactivation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9438cb8c8ec3adc84b2b450a3aab0123d074c3b
generic

quota: Fix race of dquot_scan_active() with quota deactivation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e93ab401da4b2e2c1b8ef2424de2f238d51c8b2d
generic

quota: Fix race of dquot_scan_active() with quota deactivation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ac8a2e0d287ebf35e5d7e51e260b4e146648ba4a
generic

quota: Fix race of dquot_scan_active() with quota deactivation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82cbdb4c1ebb5ea7d7bd45c18d3483b5bd32ebc1
generic

quota: Fix race of dquot_scan_active() with quota deactivation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6678dde265708003c2b42551af4a2e3cb05decd5
generic

quota: Fix race of dquot_scan_active() with quota deactivation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61e25f664dc2a08299e07d84c85776abc2350f75
generic

quota: Fix race of dquot_scan_active() with quota deactivation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2bdc80f4619411e5bd4a3ef23f51e14021ed457c

Vendor Advisories for CVE-2026-53050(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 35× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 21:03 UTCEG score recompute
  2. 2026-07-06 21:03 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 08:03 UTCEG score recompute
  6. 2026-07-06 08:03 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 19:02 UTCEG score recompute
  10. 2026-07-05 19:02 UTCGHSA enrichment
  11. 2026-07-05 06:09 UTCEG score recompute
  12. 2026-07-05 06:09 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 17:08 UTCEG score recompute
  16. 2026-07-04 17:07 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 04:10 UTCEG score recompute
  19. 2026-07-04 04:10 UTCGHSA enrichment
  20. 2026-07-03 14:47 UTCEG score recompute
  21. 2026-07-03 14:47 UTCGHSA enrichment
  22. 2026-07-03 01:55 UTCEG score recompute
  23. 2026-07-03 01:54 UTCGHSA enrichment
  24. 2026-07-02 13:02 UTCEG score recompute
  25. 2026-07-02 13:02 UTCGHSA enrichment
Show 22 more
  1. 2026-07-02 00:08 UTCEG score recompute
  2. 2026-07-02 00:08 UTCGHSA enrichment
  3. 2026-07-01 15:07 UTCEPSS rescore
  4. 2026-07-01 11:16 UTCEG score recompute
  5. 2026-07-01 11:16 UTCGHSA enrichment
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 22:23 UTCEG score recompute
  8. 2026-06-30 22:23 UTCGHSA enrichment
  9. 2026-06-30 09:31 UTCEG score recompute 7.80
  10. 2026-06-30 09:30 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 13:54 UTCEG score recompute
  18. 2026-06-27 13:54 UTCGHSA enrichment
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 18:17 UTCEG score recompute
  22. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53050?
CVE-2026-53050 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: quota: Fix race of dquotscanactive() with quota deactivation dquotscanactive() can race with quota deactivation in quotareleaseworkfn() like: CPU0 (quotareleaseworkfn) CPU1 (dquotscanactive) ==============================…
When was CVE-2026-53050 disclosed?
CVE-2026-53050 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53050 actively exploited?
CVE-2026-53050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53050?
CVE-2026-53050 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53050?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53050, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53050

Explore →

Is Your Infrastructure Affected by CVE-2026-53050?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.