CVE-2026-93150

published 17 Sep 2026 · updated 17 Nov 2026

cgroup/cpuset: Make nr_deadline_tasks an atomic_t

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4987d336abf3fa575a2d953f69e11154ac9802c3, Kernel 5.16, Kernel 6.1.191 and 11 more.

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

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=d1b4262b78cc7638642833252ae92fc586854ffb <4987d336abf3fa575a2d953f69e11154ac9802c3, >=5.15.129 <5.16, >=6.1.50 <6.1.191, >=6.4.13 <6.5, >=6c24849f5515e4966d94fa5279bdff4acf2e9489 <642648fa7595241e4d491add5007bc33f11defb5, >=6c24849f5515e4966d94fa5279bdff4acf2e9489 <78d9daf5e13ad1448b7dfebac949936710ec7565, >=6c24849f5515e4966d94fa5279bdff4acf2e9489 <95220e1f18f6321008f021abc7d6f581f64bcb82, >=6c24849f5515e4966d94fa5279bdff4acf2e9489 <e422b32e6a57269ca8164c60674a78bee85cf5fb, >=6c24849f5515e4966d94fa5279bdff4acf2e9489 <e5965ae3f7c918151b87e5c925b7978afbeaf638, =43d8cbfefa7c59bd3b5fe184535eca476d45304e, =5ac05ce5684315d0e71194a63febaf33921c3268, =6.5, =74fac5bb0d375d6b8f5e7997925063c509089c9c, >=5.10.193 <5.114987d336abf3fa575a2d953f69e11154ac9802c3, 5.16, 6.1.191, 6.5, 642648fa7595241e4d491add5007bc33f11defb5, 78d9daf5e13ad1448b7dfebac949936710ec7565, 95220e1f18f6321008f021abc7d6f581f64bcb82, e422b32e6a57269ca8164c60674a78bee85cf5fb, e5965ae3f7c918151b87e5c925b7978afbeaf638, 5.11
linux-kernel: Kernel>=5.15.129 <5.16, >=6.1.50 <6.1.191, >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.4.13 <6.5, >=6.5.0 <6.6.160, >=6.7.0 <6.12.110, >=5.10.193 <5.115.16, 6.1.191, 6.18.52, 7.2.6, 6.5, 6.6.160, 6.12.110, 5.11

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-93150 severity on Zeptric[![CVE-2026-93150](https://zeptric.io/badge/cve/CVE-2026-93150.svg)](https://zeptric.io/cve/CVE-2026-93150)