# CVE-2026-72015: fs/resctrl: Fix double-add of pseudo-locked region's RMID to free list

> A double-free vulnerability in the Linux kernel resctrl subsystem allows local attackers to cause denial of service or potentially escalate privileges.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-72015, DEBIAN-CVE-2026-72015, GHSA-wxqw-c972-64f8, UBUNTU-CVE-2026-72015

## What is CVE-2026-72015?

CVE-2026-72015 is an use after free vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

fs/resctrl: Fix double-add of pseudo-locked region's RMID to free list

A pseudo-locked group's RMID is freed when it is created. On unmount
rmdir_all_sub() unconditionally frees all RMID of all groups, resulting
in a double-free of the pseudo-locked group's RMID. The consequence of this
is that the original free results in the pseudo-locked group's RMID being
added to the rmid_free_lru linked list and the second free then attempts
to add the same RMID entry to the rmid_free_lru again.

Do not double-free a pseudo-locked group's RMID.

## Which versions are affected by CVE-2026-72015?


## How do I fix CVE-2026-72015?

Apply the vendor's patch.

## Is CVE-2026-72015 being exploited?

There is no known exploitation of CVE-2026-72015 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72015 and fix it if it is affected.

What it is: CVE-2026-72015 is an use after free vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72015 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72015/ (Markdown: https://insights.sbomify.com/CVE-2026-72015/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72015
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72015
- OSV: https://osv.dev/vulnerability/CVE-2026-72015

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72015/
Summaries are generated and may contain mistakes; the official description above is the record.