{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "395ed1ef0012e1bb1e4050e84ba0173b3623112a"
            },
            {
              "fixed": "34470cc3a8e66751030d7b777dd18d9f2acb48e8"
            },
            {
              "fixed": "31e3d833d522746a93d135e8b465d16f8ad33453"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.19.0"
            },
            {
              "fixed": "7.2.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90384.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\niomap: release the folio batch on iomap callback failures\n\nA sashiko review of an unrelated patch points out that the folio\nbatch mechanism used for iomap zero range fails to release the batch\nin a couple error scenarios. If either calls to -\u003eiomap_end() or\n-\u003eiomap_begin() fail, the direct return paths bypass the batch\ncleanup.\n\nThe -\u003eiomap_end() case is not a practical issue at the moment\nbecause there is no user of the mechanism that returns an error from\nthis path. The -\u003eiomap_begin() case is theoretically possible\nbecause XFS can invoke the fill helper and error out at various\npoints thereafter. This subtly complicates things because XFS does\nnot transfer iomap_flags to the iomap data structure in the error\npath.\n\nTo deal with both of these issues, first make sure to invoke the\ncleanup helper in the error path for either fs callback. Second,\nupdate the helper to clear the flag unconditionally and release the\nbatch so long as it is populated. This more clearly delineates the\npurpose of the flag to control the I/O path and not necessarily the\nstatus of the fbatch, so add a comment around this as well.",
  "id": "CVE-2026-90384",
  "modified": "2026-09-19T03:30:38.575410647Z",
  "published": "2026-09-17T16:09:20.536Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/31e3d833d522746a93d135e8b465d16f8ad33453"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/34470cc3a8e66751030d7b777dd18d9f2acb48e8"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90384.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90384"
    },
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    }
  ],
  "schema_version": "1.9.0",
  "summary": "iomap: release the folio batch on iomap callback failures"
}