<?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 19:58:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74645 — mm/damon/lru_sort: error out for &gt;10000 active_mem_bp</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74645</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/lru_sort: error out for &amp;gt;10000 active_mem_bp&lt;/p&gt;
&lt;p&gt;damos_quota_score() can trigger division by zero if the target value is
zero.  DAMON_LRU_SORT lets users set the target value for the hot memory
scheme via active_mem_bp parameter.  It avoids setting it as the target
value if the parameter value is zero.  However, it also sets the cold
memory scheme with a target value that is calculated as &amp;#39;10000 -
active_mem_bp + 2&amp;#39;.  Hence, if a user sets active_mem_bp 10002, the cold
memory scheme&amp;#39;s quota goal target value can be zero.  As a result,
division by zero can be triggered.  Fix by returning an error when the
user tries to start DAMON with &amp;gt;10000 active_mem_bp parameter value.&lt;/p&gt;
&lt;p&gt;It makes no sense to set active_mem_bp with 10002.  It also requires
module parameters write permission to reproduce the issue.  That said, the
consequence is quite bad.&lt;/p&gt;
&lt;p&gt;One reliable way to reproduce the issue is like below:&lt;/p&gt;
&lt;p&gt;# cd /sys/module/damon_lru_sort/parameters
    # echo 1000 &amp;gt; wmarks_high
    # echo 995 &amp;gt; wmarks_mid
    # echo 0 &amp;gt; wmarks_low
    # echo 10002 &amp;gt; active_mem_bp
    # echo Y &amp;gt; enabled
    # dmesg -w
    [...]
    [  597.421247] Oops: divide error: 0000 [#1] SMP NOPTI
    [  597.428848] RIP: 0010:damos_quota_score+0x6f/0x480&lt;/p&gt;
&lt;p&gt;This issue was discovered [1] by Sashiko.&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/lru_sort: error out for &amp;gt;10000 active_mem_bp&lt;/p&gt;
&lt;p&gt;damos_quota_score() can trigger division by zero if the target value is
zero.  DAMON_LRU_SORT lets users set the target value for the hot memory
scheme via active_mem_bp parameter.  It avoids setting it as the target
value if the parameter value is zero.  However, it also sets the cold
memory scheme with a target value that is calculated as &amp;#39;10000 -
active_mem_bp + 2&amp;#39;.  Hence, if a user sets active_mem_bp 10002, the cold
memory scheme&amp;#39;s quota goal target value can be zero.  As a result,
division by zero can be triggered.  Fix by returning an error when the
user tries to start DAMON with &amp;gt;10000 active_mem_bp parameter value.&lt;/p&gt;
&lt;p&gt;It makes no sense to set active_mem_bp with 10002.  It also requires
module parameters write permission to reproduce the issue.  That said, the
consequence is quite bad.&lt;/p&gt;
&lt;p&gt;One reliable way to reproduce the issue is like below:&lt;/p&gt;
&lt;p&gt;# cd /sys/module/damon_lru_sort/parameters
    # echo 1000 &amp;gt; wmarks_high
    # echo 995 &amp;gt; wmarks_mid
    # echo 0 &amp;gt; wmarks_low
    # echo 10002 &amp;gt; active_mem_bp
    # echo Y &amp;gt; enabled
    # dmesg -w
    [...]
    [  597.421247] Oops: divide error: 0000 [#1] SMP NOPTI
    [  597.428848] RIP: 0010:damos_quota_score+0x6f/0x480&lt;/p&gt;
&lt;p&gt;This issue was discovered [1] by Sashiko.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74645</guid>
    </item>
  </channel>
</rss>
