FKIE_CVE-2026-93150
Vulnerability from fkie_nvd - Published: 2026-09-17 17:18 - Updated: 2026-09-17 17:18
Severity
Summary
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
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/cgroup/cpuset-internal.h",
"kernel/cgroup/cpuset.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "e422b32e6a57269ca8164c60674a78bee85cf5fb",
"status": "affected",
"version": "6c24849f5515e4966d94fa5279bdff4acf2e9489",
"versionType": "git"
},
{
"lessThan": "e5965ae3f7c918151b87e5c925b7978afbeaf638",
"status": "affected",
"version": "6c24849f5515e4966d94fa5279bdff4acf2e9489",
"versionType": "git"
},
{
"lessThan": "78d9daf5e13ad1448b7dfebac949936710ec7565",
"status": "affected",
"version": "6c24849f5515e4966d94fa5279bdff4acf2e9489",
"versionType": "git"
},
{
"lessThan": "95220e1f18f6321008f021abc7d6f581f64bcb82",
"status": "affected",
"version": "6c24849f5515e4966d94fa5279bdff4acf2e9489",
"versionType": "git"
},
{
"status": "affected",
"version": "5ac05ce5684315d0e71194a63febaf33921c3268",
"versionType": "git"
},
{
"status": "affected",
"version": "43d8cbfefa7c59bd3b5fe184535eca476d45304e",
"versionType": "git"
},
{
"status": "affected",
"version": "d1b4262b78cc7638642833252ae92fc586854ffb",
"versionType": "git"
},
{
"status": "affected",
"version": "74fac5bb0d375d6b8f5e7997925063c509089c9c",
"versionType": "git"
},
{
"lessThan": "5.11",
"status": "affected",
"version": "5.10.193",
"versionType": "semver"
},
{
"lessThan": "5.16",
"status": "affected",
"version": "5.15.129",
"versionType": "semver"
},
{
"lessThan": "6.2",
"status": "affected",
"version": "6.1.50",
"versionType": "semver"
},
{
"lessThan": "6.5",
"status": "affected",
"version": "6.4.13",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"kernel/cgroup/cpuset-internal.h",
"kernel/cgroup/cpuset.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.5"
},
{
"lessThan": "6.5",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/cpuset: Make nr_deadline_tasks an atomic_t\n\nThe nr_deadline_tasks variable in the cpuset structure was introduced by\ncommit 6c24849f5515 (\"sched/cpuset: Keep track of SCHED_DEADLINE task\nin cpusets\"). It is reported by sashiko [1] that nr_deadline_tasks\ncan currently be modified by inc_dl_tasks_cs() under rq-\u003elock and\nby cpuset_attach() under cpuset_mutex. So if both updates happen\nsimultaneously, the nr_deadline_tasks variable can be corrupted leading\nto incorrect operations down the road.\n\nFix that by changing its type to atomic_t so that nr_deadline_tasks\nare always atomically updated. This fix patch is a low hanging fruit.\nIt can handle some of the races between a concurrent sched_setscheduler()\nand cpuset_can_attach()/cpuset_attach() calls, but not all of them like\nthe other issue raised by sashiko [2]. This will be handled hopefully\nin a future follow up patch.\n\n[1] https://sashiko.dev/#/patchset/20260626181923.133658-1-longman%40redhat.com\n[2] https://sashiko.dev/#/patchset/20260630033344.352702-1-longman%40redhat.com"
}
],
"id": "CVE-2026-93150",
"lastModified": "2026-09-17T17:18:10.213",
"metrics": {},
"published": "2026-09-17T17:18:10.213",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/78d9daf5e13ad1448b7dfebac949936710ec7565"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/95220e1f18f6321008f021abc7d6f581f64bcb82"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e422b32e6a57269ca8164c60674a78bee85cf5fb"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e5965ae3f7c918151b87e5c925b7978afbeaf638"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…