{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68165 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68165 is a denial of service vulnerability in Linux, published on 10 Aug 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-68165 and fix it if it is affected.\n\nWhat it is: CVE-2026-68165 is a denial of service vulnerability in Linux, published on 10 Aug 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-68165 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-68165/ (Markdown: https://insights.sbomify.com/CVE-2026-68165/index.md)","id":"CVE-2026-68165","markdown":"https://insights.sbomify.com/CVE-2026-68165/index.md","name":"CVE-2026-68165","record":{"aliases":["BELL-CVE-2026-68165","DEBIAN-CVE-2026-68165","GHSA-cpwj-jg54-5hr3","UBUNTU-CVE-2026-68165"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel warning or divide-by-zero crash in DAMON by setting empty monitoring regions, causing denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: validate ranges in damon_set_regions()\n\nDAMON core logic assumes zero length regions don't exist.  However, a few\nDAMON API callers including DAMON_SYSFS, DAMON_RECLAIM and DAMON_LRU_SORT\nallow users to set empty monitoring target regions.  This could result in\nWARN_ONCE() on CONFIG_DAMON_DEBUG_SANITY enabled kernel, and\ndivide-by-zero from damon_merge_two_regions().\n\nFor example, the WANR_ONCE() can be triggered like below.\n\n    # grep DAMON_DEBUG_SANITY /boot/config-$(uname -r)\n    # CONFIG_DAMON_DEBUG_SANITY=y\n    # damo start\n    # cd /sys/kernel/mm/damon/admin/kdamonds/0\n    # echo 0 \u003e contexts/0/targets/0/regions/0/start\n    # echo 0 \u003e contexts/0/targets/0/regions/0/end\n    # echo commit \u003e state\n    # dmesg\n    [....]\n    [   73.705780] ------------[ cut here ]------------\n    [   73.707552] start 0 \u003e= end 0\n    [   73.708452] WARNING: mm/damon/core.c:359 at damon_new_region+0x6e/0x80, CPU#1: kdamond.0/758\n    [...]\n\nAll DAMON API callers eventually use damon_set_regions() to setup the\nregions.  Add the validation logic in the function.","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: validate ranges in damon_set_regions()","id":"CVE-2026-68165","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"userfaultfd: prevent registration of special VMAs","id":"CVE-2026-68166"},"packages":[],"prev":{"headline":"mm/damon/core: disallow overlapping input ranges for damon_set_regions()","id":"CVE-2026-68164"},"products":["Linux"],"published":"2026-08-10","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-08-19","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel warning or divide-by-zero crash in DAMON by setting empty monitoring regions, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-68165/"}