FKIE_CVE-2026-90384

Vulnerability from fkie_nvd - Published: 2026-09-17 17:17 - Updated: 2026-09-17 17:17
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
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/31e3d833d522746a93d135e8b465d16f8ad33453
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/34470cc3a8e66751030d7b777dd18d9f2acb48e8
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "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-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "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."
    }
  ],
  "id": "CVE-2026-90384",
  "lastModified": "2026-09-17T17:17:37.777",
  "metrics": {},
  "published": "2026-09-17T17:17:37.777",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/31e3d833d522746a93d135e8b465d16f8ad33453"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/34470cc3a8e66751030d7b777dd18d9f2acb48e8"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.