https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 15:29:23 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-46025 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-46025 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0831 https://cve.radiocsirt.org/vuln/euvd-2026-327088 EUVD-2026-327088 https://cve.radiocsirt.org/vuln/euvd-2026-327088 https://cve.radiocsirt.org/vuln/fkie_cve-2026-46025 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/core: fix damon_call() vs kdamond_fn() exit race</p> <p>Patch series &#34;mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit race&#34;.</p> <p>damon_call() and damos_walk() can leak memory and/or deadlock when they race with kdamond terminations. Fix those.</p> <p>This patch (of 2);</p> <p>When kdamond_fn() main loop is finished, the function cancels all remaining damon_call() requests and unset the damon_ctx-&gt;kdamond so that API callers and API functions themselves can know the context is terminated. damon_call() adds the caller&#39;s request to the queue first. After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx-&gt;kdamond is set). Only if the kdamond is running, damon_call() starts waiting for the kdamond&#39;s handling of the newly added request.</p> <p>The damon_call() requests registration and damon_ctx-&gt;kdamond unset are protected by different mutexes, though. Hence, damon_call() could race with damon_ctx-&gt;kdamond unset, and result in deadlocks.</p> <p>For example, let&#39;s suppose kdamond successfully finished the damon_call() requests cancelling. Right after that, damon_call() is called for the context. It registers the new request, and shows the context is still running, because damon_ctx-&gt;kdamond unset is not yet done. Hence the damon_call() caller starts waiting for the handling of the request. However, the kdamond is already on the termination steps, so it never handles the new request. As a r…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/core: fix damon_call() vs kdamond_fn() exit race</p> <p>Patch series &#34;mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit race&#34;.</p> <p>damon_call() and damos_walk() can leak memory and/or deadlock when they race with kdamond terminations. Fix those.</p> <p>This patch (of 2);</p> <p>When kdamond_fn() main loop is finished, the function cancels all remaining damon_call() requests and unset the damon_ctx-&gt;kdamond so that API callers and API functions themselves can know the context is terminated. damon_call() adds the caller&#39;s request to the queue first. After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx-&gt;kdamond is set). Only if the kdamond is running, damon_call() starts waiting for the kdamond&#39;s handling of the newly added request.</p> <p>The damon_call() requests registration and damon_ctx-&gt;kdamond unset are protected by different mutexes, though. Hence, damon_call() could race with damon_ctx-&gt;kdamond unset, and result in deadlocks.</p> <p>For example, let&#39;s suppose kdamond successfully finished the damon_call() requests cancelling. Right after that, damon_call() is called for the context. It registers the new request, and shows the context is still running, because damon_ctx-&gt;kdamond unset is not yet done. Hence the damon_call() caller starts waiting for the handling of the request. However, the kdamond is already on the termination steps, so it never handles the new request. As a r…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-46025 https://cve.radiocsirt.org/vuln/ghsa-rhpm-rxf4-q3hf <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/core: fix damon_call() vs kdamond_fn() exit race</p> <p>Patch series &#34;mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit race&#34;.</p> <p>damon_call() and damos_walk() can leak memory and/or deadlock when they race with kdamond terminations. Fix those.</p> <p>This patch (of 2);</p> <p>When kdamond_fn() main loop is finished, the function cancels all remaining damon_call() requests and unset the damon_ctx-&gt;kdamond so that API callers and API functions themselves can know the context is terminated. damon_call() adds the caller&#39;s request to the queue first. After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx-&gt;kdamond is set). Only if the kdamond is running, damon_call() starts waiting for the kdamond&#39;s handling of the newly added request.</p> <p>The damon_call() requests registration and damon_ctx-&gt;kdamond unset are protected by different mutexes, though. Hence, damon_call() could race with damon_ctx-&gt;kdamond unset, and result in deadlocks.</p> <p>For example, let&#39;s suppose kdamond successfully finished the damon_call() requests cancelling. Right after that, damon_call() is called for the context. It registers the new request, and shows the context is still running, because damon_ctx-&gt;kdamond unset is not yet done. Hence the damon_call() caller starts waiting for the handling of the request. However, the kdamond is already on the termination steps, so it never handles the new request. As a r…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/core: fix damon_call() vs kdamond_fn() exit race</p> <p>Patch series &#34;mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit race&#34;.</p> <p>damon_call() and damos_walk() can leak memory and/or deadlock when they race with kdamond terminations. Fix those.</p> <p>This patch (of 2);</p> <p>When kdamond_fn() main loop is finished, the function cancels all remaining damon_call() requests and unset the damon_ctx-&gt;kdamond so that API callers and API functions themselves can know the context is terminated. damon_call() adds the caller&#39;s request to the queue first. After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx-&gt;kdamond is set). Only if the kdamond is running, damon_call() starts waiting for the kdamond&#39;s handling of the newly added request.</p> <p>The damon_call() requests registration and damon_ctx-&gt;kdamond unset are protected by different mutexes, though. Hence, damon_call() could race with damon_ctx-&gt;kdamond unset, and result in deadlocks.</p> <p>For example, let&#39;s suppose kdamond successfully finished the damon_call() requests cancelling. Right after that, damon_call() is called for the context. It registers the new request, and shows the context is still running, because damon_ctx-&gt;kdamond unset is not yet done. Hence the damon_call() caller starts waiting for the handling of the request. However, the kdamond is already on the termination steps, so it never handles the new request. As a r…</p> https://cve.radiocsirt.org/vuln/ghsa-rhpm-rxf4-q3hf https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 <p>kernel-devel-7.0.11-1.1 on GA media</p> <p>kernel-devel-7.0.11-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46025 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 119 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: fix damon_call() vs kdamond_fn() exit race Patch series &#34;mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit race&#34;. damon_call() and damos_walk() can leak memory and/or deadlock when they race with kdamond terminations. Fix those. This patch (of 2); When kdamond_fn() main loop is finished, the function cancels all remaining damon_call() requests and unset the damon_ctx-&gt;kdamond so that API callers and API functions themselves can know the context is terminated. damon_call() adds the caller&#39;s request to the queue first. After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx-&gt;kdamond is set). Only if the kdamond is running, damon_call() starts waiting for the kdamond&#39;s handling of the newly added request. The damon_call() requests registration and damon_ctx-&gt;kdamond unset are protected by different mutexes, though. Hence, damon_call() could race with damon_ctx-&gt;kdamond unset, and result in deadlocks. For example, let&#39;s suppose kdamond successfully finished the damon_call() requests cancelling. Right after that, damon_call() is called for the context. It registers the new request, and shows the context is still running, because damon_ctx-&gt;kdamond unset is not yet done. Hence the damon_call() caller starts waiting for the handling of the request. However, the kdamond is already on the termination steps, so it never handles the new request. As a result, the…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 119 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: fix damon_call() vs kdamond_fn() exit race Patch series &#34;mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit race&#34;. damon_call() and damos_walk() can leak memory and/or deadlock when they race with kdamond terminations. Fix those. This patch (of 2); When kdamond_fn() main loop is finished, the function cancels all remaining damon_call() requests and unset the damon_ctx-&gt;kdamond so that API callers and API functions themselves can know the context is terminated. damon_call() adds the caller&#39;s request to the queue first. After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx-&gt;kdamond is set). Only if the kdamond is running, damon_call() starts waiting for the kdamond&#39;s handling of the newly added request. The damon_call() requests registration and damon_ctx-&gt;kdamond unset are protected by different mutexes, though. Hence, damon_call() could race with damon_ctx-&gt;kdamond unset, and result in deadlocks. For example, let&#39;s suppose kdamond successfully finished the damon_call() requests cancelling. Right after that, damon_call() is called for the context. It registers the new request, and shows the context is still running, because damon_ctx-&gt;kdamond unset is not yet done. Hence the damon_call() caller starts waiting for the handling of the request. However, the kdamond is already on the termination steps, so it never handles the new request. As a result, the…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46025 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700