Menu

Star on GitHub · 3.2k

CVE-2026-72015

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.

Published Aug 15, 2026EPSS 0.22%

Overview

CVE-2026-72015 is a known-severity vulnerability. It was published on August 15, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-72015?

CVE-2026-72015 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-72015?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-72015?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-72015?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-72015 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.