Menu

Star on GitHub · 3.2k

CVE-2026-72184

In the Linux kernel, the following vulnerability has been resolved: ntfs: fix hole runlist memory leak in insert range error path ntfs_non_resident_attr_insert_range() allocates hole_rl before ma…

Published Aug 15, 2026EPSS 0.20%

Overview

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

Technical description

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

ntfs: fix hole runlist memory leak in insert range error path

ntfs_non_resident_attr_insert_range() allocates hole_rl before mapping the

whole runlist. If ntfs_attr_map_whole_runlist() fails, the error path drops

ni->runlist.lock and returns without freeing hole_rl. This leaks memory

of sizeof(*hole_rl) * 2 bytes.

Fix this memory leak by freeing hole_rl before returning from

that error path, matching the later error paths in the same function.

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-72184?

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

How severe is CVE-2026-72184?

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-72184?

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-72184?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-72184 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.