<?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 00:46:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31653 — mm/damon/sysfs: dealloc repeat_call_control if damon_call() fails</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31653</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/sysfs: dealloc repeat_call_control if damon_call() fails&lt;/p&gt;
&lt;p&gt;damon_call() for repeat_call_control of DAMON_SYSFS could fail if somehow
the kdamond is stopped before the damon_call().  It could happen, for
example, when te damon context was made for monitroing of a virtual
address processes, and the process is terminated immediately, before the
damon_call() invocation.  In the case, the dyanmically allocated
repeat_call_control is not deallocated and leaked.&lt;/p&gt;
&lt;p&gt;Fix the leak by deallocating the repeat_call_control under the
damon_call() failure.&lt;/p&gt;
&lt;p&gt;This issue is discovered by sashiko [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;mm/damon/sysfs: dealloc repeat_call_control if damon_call() fails&lt;/p&gt;
&lt;p&gt;damon_call() for repeat_call_control of DAMON_SYSFS could fail if somehow
the kdamond is stopped before the damon_call().  It could happen, for
example, when te damon context was made for monitroing of a virtual
address processes, and the process is terminated immediately, before the
damon_call() invocation.  In the case, the dyanmically allocated
repeat_call_control is not deallocated and leaked.&lt;/p&gt;
&lt;p&gt;Fix the leak by deallocating the repeat_call_control under the
damon_call() failure.&lt;/p&gt;
&lt;p&gt;This issue is discovered by sashiko [1].&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31653</guid>
    </item>
  </channel>
</rss>
