CVE-2026-93150 Affecting python3-perf6.12-debuginfo package, versions <1:6.12.110-135.201.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-AMZN2023-PYTHON3PERF612DEBUGINFO-20868530
- published13 Oct 2026
- disclosed17 Sept 2026
Introduced: 17 Sep 2026
CVE-2026-93150 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 python3-perf6.12-debuginfo to version 1:6.12.110-135.201.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3196.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python3-perf6.12-debuginfo package and not the python3-perf6.12-debuginfo package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
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
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-93150
- https://git.kernel.org/stable/c/78d9daf5e13ad1448b7dfebac949936710ec7565
- https://git.kernel.org/stable/c/95220e1f18f6321008f021abc7d6f581f64bcb82
- https://git.kernel.org/stable/c/e422b32e6a57269ca8164c60674a78bee85cf5fb
- https://git.kernel.org/stable/c/e5965ae3f7c918151b87e5c925b7978afbeaf638