Menu

Star on GitHub · 3.2k

CVE-2026-72370

In the Linux kernel, the following vulnerability has been resolved: iomap: release pages on atomic dio size mismatch If bio_iov_iter_get_pages() or the bounce helper succeeds but builds a short b…

Published Aug 15, 2026EPSS 0.21%

Overview

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

Technical description

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

iomap: release pages on atomic dio size mismatch

If bio_iov_iter_get_pages() or the bounce helper succeeds but builds a

short bio, the REQ_ATOMIC size check rejects it before submission. The

old error path only dropped the bio reference, leaving any pages already

attached to the bio unreleased.

Release or unbounce the pages before falling through to out_put_bio on

this error path.

This bug was reported by sashiko:

https://sashiko.dev/#/patchset/20260608073134.95964-1-changfengnan%40bytedance.com

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

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

How severe is CVE-2026-72370?

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

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

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