{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93099 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93099 is an use after free 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-93099 and fix it if it is affected.\n\nWhat it is: CVE-2026-93099 is an use after free 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-93099 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-93099/ (Markdown: https://insights.sbomify.com/CVE-2026-93099/index.md)","id":"CVE-2026-93099","markdown":"https://insights.sbomify.com/CVE-2026-93099/index.md","name":"CVE-2026-93099","record":{"aliases":["AZL-101933","BELL-CVE-2026-93099","DEBIAN-CVE-2026-93099","GHSA-qpj7-xpxx-33h9","UBUNTU-CVE-2026-93099"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A use-after-free in the Linux kernel resctrl subsystem allows local attackers to execute arbitrary code or escalate privileges via race conditions during CPU hotplug.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nfs/resctrl: Fix UAF from worker threads when domains are removed\n\nThe mbm_handle_overflow() and cqm_handle_limbo() workers read event counters\nand may sleep while doing so. They are scheduled via delayed_work embedded in\nstruct rdt_l3_mon_domain. Architecture allocates and frees these domains from\nCPU hotplug callbacks under cpus_write_lock(), and the workers acquire\ncpus_read_lock() to keep the domain alive across their access.\n\nA use-after-free can occur when a worker is blocked waiting for\ncpus_read_lock() while the hotplug core holds cpus_write_lock(): the\narchitecture frees the rdt_l3_mon_domain that contains the worker's\nwork_struct. When the worker unblocks, the container_of() it performs on the\nembedded work pointer dereferences freed memory.\n\nDrop cpus_read_lock() from the workers and instead drain pending and in-flight\nwork synchronously before the architecture can free the domain.  Since\narchitecture offlines the domain under cpus_write_lock() after it has been\nunlinked from the RCU list and a grace period has elapsed, no new work can be\nscheduled. The cancel only needs to wait out existing work.  Drop\nrdtgroup_mutex during CPU offline around cancel_delayed_work_sync() so that\na worker waiting on the mutex can complete before re-pinning the work on\na different CPU.\n\nWhen offlining a CPU the architecture may iterate over resources in any order.\nFor example, the MBA control domain may be offlined before or after\na corresponding L3 monitor domain. Ensure that resctrl fs cancels the workers\nno matter what order the architecture offlines the domains.","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":"fs/resctrl: Fix UAF from worker threads when domains are removed","id":"CVE-2026-93099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"fs/resctrl: Prevent use-after-free in rdtgroup_kn_put()","id":"CVE-2026-93100"},"packages":[],"prev":{"headline":"rpmsg: glink: fix deadlock in endpoint destroy during driver detach","id":"CVE-2026-93098"},"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-19","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel resctrl subsystem allows local attackers to execute arbitrary code or escalate privileges via race conditions during CPU hotplug.","url":"https://insights.sbomify.com/CVE-2026-93099/"}