<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T15:18:32.651489+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-39909</id>
    <title>CVE-2025-39909 — mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()</title>
    <updated>2026-10-01T15:18:32.751193+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/damon/lru_sort: avoid divide-by-zero in damon_lru_sort_apply_parameters()</p>
<p>Patch series "mm/damon: avoid divide-by-zero in DAMON module's parameters
application".</p>
<p>DAMON's RECLAIM and LRU_SORT modules perform no validation on
user-configured parameters during application, which may lead to
division-by-zero errors.</p>
<p>Avoid the divide-by-zero by adding validation checks when DAMON modules
attempt to apply the parameters.</p>
<p>This patch (of 2):</p>
<p>During the calculation of 'hot_thres' and 'cold_thres', either
'sample_interval' or 'aggr_interval' is used as the divisor, which may
lead to division-by-zero errors.  Fix it by directly returning -EINVAL
when such a case occurs.  Additionally, since 'aggr_interval' is already
required to be set no smaller than 'sample_interval' in damon_set_attrs(),
only the case where 'sample_interval' is zero needs to be checked.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-39909"/>
  </entry>
</feed>
