CVE-2026-93150cgroup/cpuset: Make nr_deadline_tasks an atomic_t
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: cgroup/cpuset: Make nr_deadline_tasks an atomic_t The nr_deadline_tasks variable in the cpuset structure was introduced by commit 6c24849f5515 ("sched/cpuset: Keep track of SCHED_DEADLINE task in cpusets"). It is reported by sashiko [1] that nr_deadline_tasks can currently be modified by inc_dl_tasks_cs() under rq->lock and by cpuset_attach() under cpuset_mutex. So if both updates happen simultaneously, the nr_deadline_tasks variable can be corrupted leading to incorrect operations down the road. Fix that by changing its type to atomic_t so that nr_deadline_tasks are always atomically updated. This fix patch is a low hanging fruit. It can handle some of the races between a concurrent sched_setscheduler() and cpuset_can_attach()/cpuset_attach() calls, but not all of them like the other issue raised by sashiko [2]. This will be handled hopefully in a future follow up patch. [1] https://sashiko.dev/#/patchset/20260626181923.133658-1-longman%40redhat.com [2] https://sashiko.dev/#/patchset/20260630033344.352702-1-longman%40redhat.com
Timeline
ID reserved
By Linux
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected d1b4262b78cc7638642833252ae92fc586854ffb – < 4987d336abf3fa575a2d953f69e11154ac9802c3
- affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 – < 642648fa7595241e4d491add5007bc33f11defb5
- affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 – < e422b32e6a57269ca8164c60674a78bee85cf5fb
- affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 – < e5965ae3f7c918151b87e5c925b7978afbeaf638
- affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 – < 78d9daf5e13ad1448b7dfebac949936710ec7565
- affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 – < 95220e1f18f6321008f021abc7d6f581f64bcb82
- affected 5ac05ce5684315d0e71194a63febaf33921c3268
- affected 43d8cbfefa7c59bd3b5fe184535eca476d45304e
- affected 74fac5bb0d375d6b8f5e7997925063c509089c9c
- affected 6.1.50 – < 6.1.191
- affected 5.10.193 – < 5.11
- affected 5.15.129 – < 5.16
- affected 6.4.13 – < 6.5
- affected 6.5
- unaffected < 6.5
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/4987d336abf3fa575a2d953f69e11154ac9802c3 (opens in a new tab)
- https://git.kernel.org/stable/c/642648fa7595241e4d491add5007bc33f11defb5 (opens in a new tab)
- https://git.kernel.org/stable/c/e422b32e6a57269ca8164c60674a78bee85cf5fb (opens in a new tab)
- https://git.kernel.org/stable/c/e5965ae3f7c918151b87e5c925b7978afbeaf638 (opens in a new tab)
- https://git.kernel.org/stable/c/78d9daf5e13ad1448b7dfebac949936710ec7565 (opens in a new tab)
- https://git.kernel.org/stable/c/95220e1f18f6321008f021abc7d6f581f64bcb82 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82258 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93150)Record last updated .