CVE-2026-90384 (GCVE-0-2026-90384)
Vulnerability from cvelistv5
Published
2026-09-17 16:09
Modified
2026-10-19 09:02
Severity ?
Summary
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.
References
Impacted products
Vendor Product Version
Linux Linux Version: 395ed1ef0012e1bb1e4050e84ba0173b3623112a
Version: 395ed1ef0012e1bb1e4050e84ba0173b3623112a
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/iomap/iter.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "34470cc3a8e66751030d7b777dd18d9f2acb48e8",
              "status": "affected",
              "version": "395ed1ef0012e1bb1e4050e84ba0173b3623112a",
              "versionType": "git"
            },
            {
              "lessThan": "31e3d833d522746a93d135e8b465d16f8ad33453",
              "status": "affected",
              "version": "395ed1ef0012e1bb1e4050e84ba0173b3623112a",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/iomap/iter.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.19"
            },
            {
              "lessThan": "6.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.6",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T09:02:46.849Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/34470cc3a8e66751030d7b777dd18d9f2acb48e8"
        },
        {
          "url": "https://git.kernel.org/stable/c/31e3d833d522746a93d135e8b465d16f8ad33453"
        }
      ],
      "title": "iomap: release the folio batch on iomap callback failures",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90384",
    "datePublished": "2026-09-17T16:09:20.536Z",
    "dateReserved": "2026-09-11T19:38:34.809Z",
    "dateUpdated": "2026-10-19T09:02:46.849Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.