{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90384 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90384 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90384 and fix it if it is affected.\n\nWhat it is: CVE-2026-90384 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90384 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90384/ (Markdown: https://insights.sbomify.com/CVE-2026-90384/index.md)","id":"CVE-2026-90384","markdown":"https://insights.sbomify.com/CVE-2026-90384/index.md","name":"CVE-2026-90384","record":{"aliases":["DEBIAN-CVE-2026-90384","GHSA-7vw7-23g3-j252","UBUNTU-CVE-2026-90384"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A Linux kernel bug in iomap fails to release folio batches on error, potentially causing memory leaks or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"iomap: release the folio batch on iomap callback failures","id":"CVE-2026-90384","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"md/raid1: create serial pool adding rdev to array with serialize_policy=1","id":"CVE-2026-90385"},"packages":[],"prev":{"headline":"misc: sgi-gru: remove interrupt-context page-table walks","id":"CVE-2026-90383"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A Linux kernel bug in iomap fails to release folio batches on error, potentially causing memory leaks or denial of service.","url":"https://insights.sbomify.com/CVE-2026-90384/"}