cgroup/cpuset: Make nr_deadline_tasks an atomic_t
Summary
| CVE | CVE-2026-93150 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:18:10 UTC |
| Updated | 2026-09-17 17:18:10 UTC |
| 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 |
Risk And Classification
EPSS: 0.002000000 probability, percentile 0.101490000 (date 2026-09-18)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 e422b32e6a57269ca8164c60674a78bee85cf5fb git | Not specified |
| CNA | Linux | Linux | affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 e5965ae3f7c918151b87e5c925b7978afbeaf638 git | Not specified |
| CNA | Linux | Linux | affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 78d9daf5e13ad1448b7dfebac949936710ec7565 git | Not specified |
| CNA | Linux | Linux | affected 6c24849f5515e4966d94fa5279bdff4acf2e9489 95220e1f18f6321008f021abc7d6f581f64bcb82 git | Not specified |
| CNA | Linux | Linux | affected 5ac05ce5684315d0e71194a63febaf33921c3268 git | Not specified |
| CNA | Linux | Linux | affected 43d8cbfefa7c59bd3b5fe184535eca476d45304e git | Not specified |
| CNA | Linux | Linux | affected d1b4262b78cc7638642833252ae92fc586854ffb git | Not specified |
| CNA | Linux | Linux | affected 74fac5bb0d375d6b8f5e7997925063c509089c9c git | Not specified |
| CNA | Linux | Linux | affected 5.10.193 5.11 semver | Not specified |
| CNA | Linux | Linux | affected 5.15.129 5.16 semver | Not specified |
| CNA | Linux | Linux | affected 6.1.50 6.2 semver | Not specified |
| CNA | Linux | Linux | affected 6.4.13 6.5 semver | Not specified |
| CNA | Linux | Linux | affected 6.5 | Not specified |
| CNA | Linux | Linux | unaffected 6.5 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.110 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.52 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.6 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/95220e1f18f6321008f021abc7d6f581f64bcb82 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/78d9daf5e13ad1448b7dfebac949936710ec7565 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e5965ae3f7c918151b87e5c925b7978afbeaf638 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e422b32e6a57269ca8164c60674a78bee85cf5fb | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.