CVE-2026-53050 — 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 12a820a9923c11e8e898da9f82c8aded70cdcd16 and < ac8a2e0d287ebf35e5d7e51e260b4e146648ba4aversion 6.6≥ 6.5.8 and < 6.6≥ 5.4.259 and < 5.5≥ 4.19.297 and < 4.20≥ 6.1.59 and < 6.1.175≥ 5.15.136 and < 5.15.209≥ 5.10.199 and < 5.10.258 and 10 moreversion 2a1ddddba6541143c8f73962f3021f1789114284version 061a18239ced5eb086967a2b4451cb1cc5ce0702version bb7e3a019b52d829949d02b64ebab37838148fbf≥ 869b6ea1609f655a43251bf41757aa44e5350a8f and < e93ab401da4b2e2c1b8ef2424de2f238d51c8b2d≥ 869b6ea1609f655a43251bf41757aa44e5350a8f and < 82cbdb4c1ebb5ea7d7bd45c18d3483b5bd32ebc1≥ 869b6ea1609f655a43251bf41757aa44e5350a8f and < fdd424d7c35633ac577fd87d1b043d1b8a6cd350≥ 869b6ea1609f655a43251bf41757aa44e5350a8f and < 61e25f664dc2a08299e07d84c85776abc2350f75≥ 869b6ea1609f655a43251bf41757aa44e5350a8f and < 6678dde265708003c2b42551af4a2e3cb05decd5≥ 56e96b38d2f7cd95b3c30eb70decac7233915e0a and < f9438cb8c8ec3adc84b2b450a3aab0123d074c3b≥ 22c06bf1f99ec3ec16b1a81342becba4c59a1f16 and < 2bdc80f4619411e5bd4a3ef23f51e14021ed457c |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
≥ 4.19.297 and < 4.20version 6.6-rc7version 6.6-rc6version 6.6≥ 6.19 and < 7.0.10≥ 6.13 and < 6.18.33≥ 6.7 and < 6.12.91≥ 6.6.1 and < 6.6.141 and 5 more≥ 6.5.8 and < 6.6≥ 6.1.59 and < 6.1.175≥ 5.15.136 and < 5.15.209≥ 5.10.199 and < 5.10.258≥ 5.4.259 and < 5.5 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.10%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 7.8
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
12 on the record
- git.kernel.org/stable/c/6678dde265708003c2b42551af4a2e3cb05decd5
- git.kernel.org/stable/c/82cbdb4c1ebb5ea7d7bd45c18d3483b5bd32ebc1
- git.kernel.org/stable/c/fdd424d7c35633ac577fd87d1b043d1b8a6cd350
- git.kernel.org/stable/c/e93ab401da4b2e2c1b8ef2424de2f238d51c8b2d
- git.kernel.org/stable/c/2bdc80f4619411e5bd4a3ef23f51e14021ed457c
- git.kernel.org/stable/c/f9438cb8c8ec3adc84b2b450a3aab0123d074c3b
- git.kernel.org/stable/c/ac8a2e0d287ebf35e5d7e51e260b4e146648ba4a
- git.kernel.org/stable/c/61e25f664dc2a08299e07d84c85776abc2350f75
- github.com/advisories/GHSA-4mf5-rjc5-62qc
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- nvd.nist.gov/vuln/detail/CVE-2026-53050
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 14h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 14h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-53050 is "quota: Fix race of dquot_scan_active() with quota deactivation", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.