Skip to main content
VulnerabilityPublished Updated

CVE-2026-93099: Linux kernel · fs/resctrl: Fix UAF from worker threads when domains are removed

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in b86dbfe4583bf134932a6cc45bf25b12c10a0b2f : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in b86dbfe4583bf134932a6cc45bf25b12c10a0b2f, 2566b5cd6a275c124e8f154fef6e815f92ec8d5c, 6a2e023429a41afd0d9dfe74268aa51774a953ff

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to b86dbfe4583bf134932a6cc45bf25b12c10a0b2f, 2566b5cd6a275c124e8f154fef6e815f92ec8d5c or 6a2e023429a41afd0d9dfe74268aa51774a953ff.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 24247aeeabe99eab13b798ccccc2dec066dd6f07, < b86dbfe4583bf134932a6cc45bf25b12c10a0b2f
Fixed in
  • b86dbfe4583bf134932a6cc45bf25b12c10a0b2f
LinuxLinuxAffected
  • ≥ 24247aeeabe99eab13b798ccccc2dec066dd6f07, < 2566b5cd6a275c124e8f154fef6e815f92ec8d5c
Fixed in
  • 2566b5cd6a275c124e8f154fef6e815f92ec8d5c
LinuxLinuxAffected
  • ≥ 24247aeeabe99eab13b798ccccc2dec066dd6f07, < 6a2e023429a41afd0d9dfe74268aa51774a953ff
Fixed in
  • 6a2e023429a41afd0d9dfe74268aa51774a953ff
LinuxLinuxAffected
  • =4.14
Fixed in–

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.

References

Community reviews

Loading reviews…