GHSA-CPWJ-JG54-5HR3

Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-19 18:32
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

mm/damon/core: validate ranges in damon_set_regions()

DAMON core logic assumes zero length regions don't exist. However, a few DAMON API callers including DAMON_SYSFS, DAMON_RECLAIM and DAMON_LRU_SORT allow users to set empty monitoring target regions. This could result in WARN_ONCE() on CONFIG_DAMON_DEBUG_SANITY enabled kernel, and divide-by-zero from damon_merge_two_regions().

For example, the WANR_ONCE() can be triggered like below.

# grep DAMON_DEBUG_SANITY /boot/config-$(uname -r)
# CONFIG_DAMON_DEBUG_SANITY=y
# damo start
# cd /sys/kernel/mm/damon/admin/kdamonds/0
# echo 0 > contexts/0/targets/0/regions/0/start
# echo 0 > contexts/0/targets/0/regions/0/end
# echo commit > state
# dmesg
[....]
[   73.705780] ------------[ cut here ]------------
[   73.707552] start 0 >= end 0
[   73.708452] WARNING: mm/damon/core.c:359 at damon_new_region+0x6e/0x80, CPU#1: kdamond.0/758
[...]

All DAMON API callers eventually use damon_set_regions() to setup the regions. Add the validation logic in the function.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-68165"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-10T13:20:02Z",
    "severity": null
  },
  "details": "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\u0027t 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.",
  "id": "GHSA-cpwj-jg54-5hr3",
  "modified": "2026-08-19T18:32:08Z",
  "published": "2026-08-10T15:33:38Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68165"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1292c0ecb1caefb8ca064a3639d5673991e8810c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/43aaddd0fa92010a68adeda7744c7cf497a1c8e9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4b6f1d6d5d07855bd1bb9e64922b049062138bfa"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/71cf8a3ee1c18cfa8b88cc14bac9c2f43dd29f9b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b585facbafbb5cf117b37b1c75819ac046646c27"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c927b73a5694c735314ea10e7c81c07f9bd51ad7"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.