{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93150 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93150 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93150 and fix it if it is affected.\n\nWhat it is: CVE-2026-93150 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93150 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93150/ (Markdown: https://insights.sbomify.com/CVE-2026-93150/index.md)","id":"CVE-2026-93150","markdown":"https://insights.sbomify.com/CVE-2026-93150/index.md","name":"CVE-2026-93150","record":{"aliases":["AZL-101855","BELL-CVE-2026-93150","DEBIAN-CVE-2026-93150","GHSA-rm22-rvmg-2466","UBUNTU-CVE-2026-93150"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel cpuset subsystem can corrupt task counters, potentially leading to system instability or privilege escalation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"cgroup/cpuset: Make nr_deadline_tasks an atomic_t","id":"CVE-2026-93150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"nvmet-rdma: fix response resource leak on queue teardown","id":"CVE-2026-93151"},"packages":[],"prev":{"headline":"wifi: mac80211_hwsim: avoid NULL skb in stop queue drain","id":"CVE-2026-93149"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A race condition in the Linux kernel cpuset subsystem can corrupt task counters, potentially leading to system instability or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-93150/"}