Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68164mm/damon/core: disallow overlapping input ranges for damon_set_regions()

Description

In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: disallow overlapping input ranges for damon_set_regions() damon_set_regions() assumes the input ranges are sorted by the address and don't overlap each other. Hence the assumption was initially to be explicitly validated. But commit 97d482f4592f ("mm/damon/sysfs: reuse damon_set_regions() for regions setting") has mistakenly removed the validation. This can make DAMON behave in unexpected ways. At the best, the monitoring results snapshot will just look weird since there will be overlapping regions. DAMOS will also work weirdly, applying the same action multiple times for overlapping regions, and make DAMOS quota weird. More seriously, depending on the setup and regions updates sequence, negative size regions can be made. It will trigger WARN_ONCE() if the kernel is built with CONFIG_DAMON_DEBUG_SANITY=y. Depending on the monitoring results, the negative size region can further trigger division by zero in damon_merge_two_regions(). Note that some of the consequences including the WARN_ONCE() and the divide by zero depend on commits that were introduced after the root cause commit 97d482f4592f ("mm/damon/sysfs: reuse damon_set_regions() for regions setting"). Fix the problems by checking the assumption and returning an error if the input ranges don't meet the assumption. The issue was discovered [1] by Sashiko.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 97d482f4592fde2322c319f07bc54f3a0d37861c – < a5c453fffb6f2ce75fc10b5d8bc475f1758010bd
    • affected 97d482f4592fde2322c319f07bc54f3a0d37861c – < 4b4a3e7ef7bb622237495db9ba4dfd7417d6530e
    • affected 97d482f4592fde2322c319f07bc54f3a0d37861c – < 06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd
    • affected 97d482f4592fde2322c319f07bc54f3a0d37861c – < 6ce0db97fb37ab8cf8596edca0e3de8618ab009a
    • affected 97d482f4592fde2322c319f07bc54f3a0d37861c – < e33adf96afb5883f84b0d98747976bde293e33cb
    • affected 97d482f4592fde2322c319f07bc54f3a0d37861c – < 954157679ec34661c2e87e7eb796104a797c32db
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68164 badge
[![CVE-2026-68164](https://cveledger.app/badge/CVE-2026-68164.svg)](https://cveledger.app/cve/CVE-2026-68164)

Record last updated .