Skip to main content

Linux Kernel CVE-2026-72080

| EUVDEUVD-2026-59038 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-3mx4-vrgg-r9xh
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Race condition timing dependency warrants AC:H over the vendor-assigned AC:L; PR:L required to open resctrl event files; local-only vector due to filesystem mount requirement.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.3 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 06:41 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 06:21 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

fs/resctrl: Fix use-after-free during unmount

During unmount or failure teardown all mon_data structures that contain monitoring event file private data are freed after which kernfs nodes are removed. However, the RDT_DELETED flag is never set for the statically allocated default resource group.

A concurrent reader of an event file associated with the default resource group may, after dropping kernfs active protection, block on rdtgroup_mutex while unmount proceeds to free the file private data and destroy the kernfs node without waiting for the reader.

When the mutex is released, the reader wakes up, observes that RDT_DELETED is not set for the default group, and dereferences the already-freed file private data.

The scenario can be depicted as follows: CPU0 CPU1 /*

  • Default resource group's
  • monitoring data accessible via
  • kernfs file with kernfs_node::priv
  • pointing to a struct mon_data.
  • User opens the file for reading.

*/ rdtgroup_mondata_show() /* arch encounters fatal error */ rdtgroup_kn_lock_live() resctrl_exit() atomic_inc(&rdtgroup_default.waitcount) cpus_read_lock() kernfs_break_active_protection(kn) mutex_lock(&rdtgroup_mutex) cpus_read_lock() resctrl_fs_teardown() mutex_lock(&rdtgroup_mutex) rmdir_all_sub() mon_put_kn_priv() /* Delete all mon_data structures */ rdtgroup_destroy_root() kernfs_destroy_root() rdtgroup_default.kn = NULL mutex_unlock(&rdtgroup_mutex) /*

  • rdtgroup_default.flags is empty so
  • rdtgroup_kn_lock_live() returns
  • &rdtgroup_default

*/ md = of->kn->priv;

/* md points to freed mon_data */

Set RDT_DELETED for the default group unconditionally since the flag does not lead to the freeing of this statically allocated group.

Do not allow a new resctrl mount if there are any waiters on default group of previous mount. A new mount will re-initialize the default group that would appear to waiters from previous mount as though the default group is accessible causing them to access the mon_data structures from the previous mount that have been removed.

AnalysisAI

Use-after-free in the Linux kernel's resctrl filesystem subsystem allows a local low-privileged user to dereference freed kernel memory during a race between a concurrent monitoring file reader and resctrl unmount or fatal teardown. The vulnerable code path affects multiple stable kernel series, with fixes confirmed in 6.18.42, 7.1.5, and 7.2-rc3. No public exploit code has been identified at time of analysis, and the EPSS score of 0.21% reflects low current exploitation probability, though kernel use-after-free primitives are commonly developed into local privilege escalation exploits.

Technical ContextAI

The vulnerability resides in fs/resctrl, the Linux kernel subsystem implementing Intel RDT (Resource Director Technology) and AMD QoS monitoring via a pseudo-filesystem typically mounted at /sys/fs/resctrl. The bug is a race condition between rdtgroup_mondata_show() - a kernfs file read handler for monitoring event files - and resctrl_exit() invoked during unmount or fatal error teardown. The root cause is that RDT_DELETED, a lifecycle flag used to signal active readers that a resource group has been torn down, was never set on rdtgroup_default, the statically-allocated default resource group. During teardown, all mon_data structures (which carry per-event file private data and are referenced by kernfs_node::priv) are freed and kernfs nodes destroyed. A concurrent reader that has incremented rdtgroup_default.waitcount and dropped kernfs active protection via kernfs_break_active_protection() will block on rdtgroup_mutex. When unmount releases the mutex, the reader resumes, finds RDT_DELETED not set on the default group, and proceeds to dereference of->kn->priv - now a dangling pointer to freed memory. The fix unconditionally sets RDT_DELETED for the default group during teardown and blocks new resctrl mounts while waiters from a prior mount remain pending. While CWE is listed as N/A in the record, this is functionally CWE-416 (Use After Free) with a race condition element (CWE-362) as the enabling mechanism.

RemediationAI

The primary fix is to upgrade to a patched kernel: 6.18.42 or later in the 6.18 stable series, 7.1.5 or later in the 7.1 series, or 7.2-rc3 or later for the mainline series. Upstream patch commits are confirmed at https://git.kernel.org/stable/c/52fce648607e0d6a76eeb443d78708c49df1c554 (6.18), https://git.kernel.org/stable/c/7b7bb07efe41bb646a93c4624aa2bb35df190342 (7.1), and https://git.kernel.org/stable/c/7d330a1d663381579b9d5dafa642b1b3158a0ce2 (7.2-rc3). Distribution-specific backports should be tracked through the relevant vendor security channels. For systems where immediate kernel upgrade is not feasible, unmounting the resctrl filesystem ('umount /sys/fs/resctrl') and preventing remounting via systemd unit constraints or kernel lockdown policies eliminates the vulnerable code path entirely; the trade-off is loss of Intel RDT and AMD QoS monitoring capabilities, which may impact cache-aware workload scheduling or performance monitoring pipelines. If resctrl must remain active, restrict access to /sys/fs/resctrl/mon_data/ to trusted administrative users only via filesystem permissions, reducing the population capable of triggering the race.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-72080 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy