<?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://cve.radiocsirt.org</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, 06 Oct 2026 00:00:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74643 — samples/damon/mtier: error out for zero quota goal target values</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-74643</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;samples/damon/mtier: error out for zero quota goal target values&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/damon: avoid division by zero from damos_quota_score()&amp;#34;.&lt;/p&gt;
&lt;p&gt;DAMON_SAMPLE_MTIER and DAMON_LRU_SORT allow the user to trigger division
by zero in damos_quota_score().  Avoid it by adding parameters validation
checks.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;damos_quota_score() can trigger division by zero if the target_value is
zero.  DAMON_SAMPLE_MTIER lets users set the target_value via
node0_mem_{used,free}_bp parameters.  It doesn&amp;#39;t guard zero value case,
though.  As a result, users can trigger division by zero.  Fix the issue
by returning an error when the user tries to start DAMON with zero
node0_mem_{used,free}_bp parameter values.&lt;/p&gt;
&lt;p&gt;DAMON_SAMPLE_MTIER is just a sample module, but the consequence is quite
bad.  Also the zero node0_mem_free_bp parameter might look like a
reasonable setup to some users.  Hence, the issue might really happen in
the real world.&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_sample_mtier/parameters
    # echo 4096 &amp;gt; node0_start_addr
    # echo 8192 &amp;gt; node0_end_addr
    # echo 8192 &amp;gt; node1_start_addr
    # echo 81920 &amp;gt; node1_end_addr
    # echo 0 &amp;gt; node0_mem_free_bp
    # echo Y &amp;gt; enabled
    # dmesg -w
    [...]
    [18792.235916] Oops: divide error: 0000 [#1] SMP NOPTI
    [...]
    [18792.242787] RIP: 0010:damos_quota_score+0x6f/0x480
    [...]&lt;/p&gt;
&lt;p&gt;This issue was discovered [1]…&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;samples/damon/mtier: error out for zero quota goal target values&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm/damon: avoid division by zero from damos_quota_score()&amp;#34;.&lt;/p&gt;
&lt;p&gt;DAMON_SAMPLE_MTIER and DAMON_LRU_SORT allow the user to trigger division
by zero in damos_quota_score().  Avoid it by adding parameters validation
checks.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;damos_quota_score() can trigger division by zero if the target_value is
zero.  DAMON_SAMPLE_MTIER lets users set the target_value via
node0_mem_{used,free}_bp parameters.  It doesn&amp;#39;t guard zero value case,
though.  As a result, users can trigger division by zero.  Fix the issue
by returning an error when the user tries to start DAMON with zero
node0_mem_{used,free}_bp parameter values.&lt;/p&gt;
&lt;p&gt;DAMON_SAMPLE_MTIER is just a sample module, but the consequence is quite
bad.  Also the zero node0_mem_free_bp parameter might look like a
reasonable setup to some users.  Hence, the issue might really happen in
the real world.&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_sample_mtier/parameters
    # echo 4096 &amp;gt; node0_start_addr
    # echo 8192 &amp;gt; node0_end_addr
    # echo 8192 &amp;gt; node1_start_addr
    # echo 81920 &amp;gt; node1_end_addr
    # echo 0 &amp;gt; node0_mem_free_bp
    # echo Y &amp;gt; enabled
    # dmesg -w
    [...]
    [18792.235916] Oops: divide error: 0000 [#1] SMP NOPTI
    [...]
    [18792.242787] RIP: 0010:damos_quota_score+0x6f/0x480
    [...]&lt;/p&gt;
&lt;p&gt;This issue was discovered [1]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-74643</guid>
    </item>
  </channel>
</rss>
