CVE-2026-93099
Last modified
CVE-2026-93099 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: fs/resctrl: Fix UAF from worker threads when domains are removed The mbm_handle_overflow() and cqm_handle_limbo() workers read event counters and may sleep while doing so. They are scheduled via delayed_work embedded in struct rdt_l3_mon_domain.
Description
In the Linux kernel, the following vulnerability has been resolved: fs/resctrl: Fix UAF from worker threads when domains are removed The mbm_handle_overflow() and cqm_handle_limbo() workers read event counters and may sleep while doing so. They are scheduled via delayed_work embedded in struct rdt_l3_mon_domain. Architecture allocates and frees these domains from CPU hotplug callbacks under cpus_write_lock(), and the workers acquire cpus_read_lock() to keep the domain alive across their access. A use-after-free can occur when a worker is blocked waiting for cpus_read_lock() while the hotplug core holds cpus_write_lock(): the architecture frees the rdt_l3_mon_domain that contains the worker's work_struct. When the worker unblocks, the container_of() it performs on the embedded work pointer dereferences freed memory. Drop cpus_read_lock() from the workers and instead drain pending and in-flight work synchronously before the architecture can free the domain. Since architecture offlines the domain under cpus_write_lock() after it has been unlinked from the RCU list and a grace period has elapsed, no new work can be scheduled. The cancel only needs to wait out existing work. Drop rdtgroup_mutex during CPU offline around cancel_delayed_work_sync() so that a worker waiting on the mutex can complete before re-pinning the work on a different CPU. When offlining a CPU the architecture may iterate over resources in any order. For example, the MBA control domain may be offlined before or after a corresponding L3 monitor domain. Ensure that resctrl fs cancels the workers no matter what order the architecture offlines the domains.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 24247aeeabe99eab13b798ccccc2dec066dd6f07, < b86dbfe4583bf134932a6cc45bf25b12c10a0b2f; >= 24247aeeabe99eab13b798ccccc2dec066dd6f07, < 2566b5cd6a275c124e8f154fef6e815f92ec8d5c |
| Linux | Linux | 4.14 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93099?
How severe is CVE-2026-93099?
How do I fix CVE-2026-93099?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-93093In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93094In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93095In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-93096In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93097In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93098In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93100In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93101In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93102In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93103In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93104In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93105In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-93099?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
