{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90005 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90005 is a memory corruption vulnerability in Linux, published on 16 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-90005 and fix it if it is affected.\n\nWhat it is: CVE-2026-90005 is a memory corruption vulnerability in Linux, published on 16 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-90005 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-90005/ (Markdown: https://insights.sbomify.com/CVE-2026-90005/index.md)","id":"CVE-2026-90005","markdown":"https://insights.sbomify.com/CVE-2026-90005/index.md","name":"CVE-2026-90005","record":{"aliases":["BELL-CVE-2026-90005","DEBIAN-CVE-2026-90005","GHSA-rjc9-q3q5-8f95","UBUNTU-CVE-2026-90005"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A local attacker with admin privileges can trigger a memory leak and potential use-after-free in the DAMON wsse sample module, leading to denial of service or privilege escalation.","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\nsamples/damon/wsse: handle damon_start() failure\n\nPatch series \"samples/damon: handle damon_{start,stop}() failures\".\n\nAll DAMON sample modules are not correctly handling failures from\ndamon_start().  Among those, mtier also has an additional problem for\nhandling of damon_stop() failures.  wsse and prcl also have a problem in\ntheir damon_call() failure handling.  As a result, memory leaks, next\nDAMON operation disruptions, and use-after-free can happen.  Fix those.\n\nNote that only the damon_start() failure caused issues can reliably be\nreproduced.  Reproducing those issues require the admin permission,\nthough.\n\nThis patch (of 6):\n\ndamon_sample_wsse_start() callers assume it will clean up resources when\nit fails.  And the function does the cleanup for context buildup failures.\nHowever, it is not doing the cleanup for damon_start() failure.  As a\nresult, when damon_start() fails, it leaks the memory for DAMON context. \nFree the context in case of the failure to fix the issues.\n\nNote that the issue can reliably be reproduced because the module calls\ndamon_start() in the exclusive mode.  For example,\n\n    $ sudo damo start\n    $ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid\n    $ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled\n    $ sudo cat /proc/allocinfo | grep damon_new_ctx\n\nBecause the first command is running another DAMON instance, the third\ncommand fails the damon_start() call because the new DAMON instance cannot\nexclusively run.  And without this fix, by repeating the third and the\nfourth commands above, we can show the memory consumption is only\nincreasing due to the leaks.  It requires the sudo permission though.\n\nThe 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":"samples/damon/wsse: handle damon_start() failure","id":"CVE-2026-90005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"samples/damon/mtier: handle damon_stop() failure","id":"CVE-2026-90006"},"packages":[],"prev":{"headline":"mm/damon/core: handle region split failure in apply_min_nr_regions()","id":"CVE-2026-90004"},"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 local attacker with admin privileges can trigger a memory leak and potential use-after-free in the DAMON wsse sample module, leading to denial of service or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-90005/"}