{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90004 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90004 is a vulnerability in Linux, published on 16 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-90004 and fix it if it is affected.\n\nWhat it is: CVE-2026-90004 is a vulnerability in Linux, published on 16 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-90004 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-90004/ (Markdown: https://insights.sbomify.com/CVE-2026-90004/index.md)","id":"CVE-2026-90004","markdown":"https://insights.sbomify.com/CVE-2026-90004/index.md","name":"CVE-2026-90004","record":{"aliases":["DEBIAN-CVE-2026-90004","GHSA-fxh6-hh4r-jg4j","UBUNTU-CVE-2026-90004"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A null pointer dereference in the Linux kernel DAMON subsystem can cause memory corruption or crashes when region splitting fails due to allocation errors.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nmm/damon/core: handle region split failure in apply_min_nr_regions()\n\ndamon_apply_min_nr_regions() repeatedly split each region until its size\nbecomes small enough to meet the user-defined low limit of the number of\nregions.  The loop assumes the split operation (damon_split_region_at())\nwill always succeed and create the new region.  But the operation could\nsilently fail for memory allocation failures, for example.\n\nIf such failure happens and the region was the last region, the linked\nlist-based next region fetching returns invalid pointer.  As a result,\ninvalid memory dereference and corruption could happen.  Even if the\ncorner case is handled, it imposes stress to the allocator by trying split\nregions for other targets.  Fix the issue by breaking all the loops for\nany region split failure.\n\nThis means there could be a min_nr_regions violation.  It will only rarely\nhappen since the allocation is arguably too small to fail.  Even if it\nhappens, it is only temporal.  damon_apply_min_nr_regions() will be called\nagain after the aggregation interval.\n\nThe user impact of the issue should be minor, since the allocation is\narguably too small to fail.  But, it could still theoretically happen, and\nthe consequence is very bad.\n\nThis issue was discovered [1] by Sashiko.","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":"mm/damon/core: handle region split failure in apply_min_nr_regions()","id":"CVE-2026-90004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"samples/damon/wsse: handle damon_start() failure","id":"CVE-2026-90005"},"packages":[],"prev":{"headline":"futex: Prevent rcuwait use-after-free during requeue PI","id":"CVE-2026-90003"},"products":["Linux"],"published":"2026-09-16","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 null pointer dereference in the Linux kernel DAMON subsystem can cause memory corruption or crashes when region splitting fails due to allocation errors.","url":"https://insights.sbomify.com/CVE-2026-90004/"}