CVE-2026-93150: Linux Vulnerability

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

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 6c24849f5515e4966d94fa5279bdff4acf2e9489, < e422b32e6a57269ca8164c60674a78bee85cf5fb; >= 6c24849f5515e4966d94fa5279bdff4acf2e9489, < e5965ae3f7c918151b87e5c925b7978afbeaf638; >= 6c24849f5515e4966d94fa5279bdff4acf2e9489, < 78d9daf5e13ad1448b7dfebac949936710ec7565; >= 6c24849f5515e4966d94fa5279bdff4acf2e9489, < 95220e1f18f6321008f021abc7d6f581f64bcb82; 5ac05ce5684315d0e71194a63febaf33921c3268; 43d8cbfefa7c59bd3b5fe184535eca476d45304e; d1b4262b78cc7638642833252ae92fc586854ffb; 74fac5bb0d375d6b8f5e7997925063c509089c9c; >= 5.10.193, < 5.11; >= 5.15.129, < 5.16; >= 6.1.50, < 6.2; >= 6.4.13, < 6.5
Linux	Linux	6.5

References

Timeline

Published: Sep 17, 2026
Last Modified: Sep 17, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-93150?

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

How severe is CVE-2026-93150?

Severity scoring for CVE-2026-93150 is pending analysis.

How do I fix CVE-2026-93150?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →