{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72176 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72176 is a vulnerability in Linux, published on 15 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-72176 and fix it if it is affected.\n\nWhat it is: CVE-2026-72176 is a vulnerability in Linux, published on 15 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-72176 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-72176/ (Markdown: https://insights.sbomify.com/CVE-2026-72176/index.md)","id":"CVE-2026-72176","markdown":"https://insights.sbomify.com/CVE-2026-72176/index.md","name":"CVE-2026-72176","record":{"aliases":["BELL-CVE-2026-72176","DEBIAN-CVE-2026-72176","GHSA-vpg8-qvx8-2ch6","UBUNTU-CVE-2026-72176"],"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":"low_privilege","summary":"A local attacker can trigger a kernel crash via null pointer dereference in DAMON sysfs schemes due to incorrect error handling in directory setup.","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/sysfs-schemes: put stats for scheme_add_dirs() internal error\n\ndamon_sysfs_scheme_add_dirs() setup the tried_regions directory after the\nstats directory setup is completed.  When the tried_regions directory\nsetup is failed, the setup function ensures the reference for the tried\nregions directory is released.  Hence the error path should put references\non setup succeeded directory objects, starting from the stats directory. \nHowever, the error path is putting the tried_regions directory instead of\nthe stats directory.\n\nAs a direct result, the stats directory object is leaked.  Worse yet, if\nthe tried_regions directory setup failed from the initial allocation, the\nscheme-\u003etried_regions field remains uninitialized.  The following\nkobject_put(\u0026scheme-\u003etried_regions-\u003ekobj) call in the error path will\ndereference the uninitialized memory.  The setup failures should not be\ncommon.  But once it happens, the consequence is quite bad.\n\nFix this issue by correctly putting the stats directory instead of the\ntried_regions directory.\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":"mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error","id":"CVE-2026-72176","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs()","id":"CVE-2026-72177"},"packages":[],"prev":{"headline":"fs/proc/task_mmu: fix make_uffd_wp_huge_pte() prot-update race","id":"CVE-2026-72175"},"products":["Linux"],"published":"2026-08-15","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-17","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel crash via null pointer dereference in DAMON sysfs schemes due to incorrect error handling in directory setup.","url":"https://insights.sbomify.com/CVE-2026-72176/"}