<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 22:58:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68165 — mm/damon/core: validate ranges in damon_set_regions()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68165</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/damon/core: validate ranges in damon_set_regions()&lt;/p&gt;
&lt;p&gt;DAMON core logic assumes zero length regions don&amp;#39;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().&lt;/p&gt;
&lt;p&gt;For example, the WANR_ONCE() can be triggered like below.&lt;/p&gt;
&lt;p&gt;# 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 &amp;gt; contexts/0/targets/0/regions/0/start
    # echo 0 &amp;gt; contexts/0/targets/0/regions/0/end
    # echo commit &amp;gt; state
    # dmesg
    [....]
    [   73.705780] ------------[ cut here ]------------
    [   73.707552] start 0 &amp;gt;= end 0
    [   73.708452] WARNING: mm/damon/core.c:359 at damon_new_region+0x6e/0x80, CPU#1: kdamond.0/758
    [...]&lt;/p&gt;
&lt;p&gt;All DAMON API callers eventually use damon_set_regions() to setup the
regions.  Add the validation logic in the function.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/damon/core: validate ranges in damon_set_regions()&lt;/p&gt;
&lt;p&gt;DAMON core logic assumes zero length regions don&amp;#39;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().&lt;/p&gt;
&lt;p&gt;For example, the WANR_ONCE() can be triggered like below.&lt;/p&gt;
&lt;p&gt;# 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 &amp;gt; contexts/0/targets/0/regions/0/start
    # echo 0 &amp;gt; contexts/0/targets/0/regions/0/end
    # echo commit &amp;gt; state
    # dmesg
    [....]
    [   73.705780] ------------[ cut here ]------------
    [   73.707552] start 0 &amp;gt;= end 0
    [   73.708452] WARNING: mm/damon/core.c:359 at damon_new_region+0x6e/0x80, CPU#1: kdamond.0/758
    [...]&lt;/p&gt;
&lt;p&gt;All DAMON API callers eventually use damon_set_regions() to setup the
regions.  Add the validation logic in the function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68165</guid>
    </item>
  </channel>
</rss>
