https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 19:12:30 +0000 https://vulnerability.circl.lu/vuln/cve-2026-90005 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>samples/damon/wsse: handle damon_start() failure</p> <p>Patch series &#34;samples/damon: handle damon_{start,stop}() failures&#34;.</p> <p>All DAMON sample modules are not correctly handling failures from damon_start(). Among those, mtier also has an additional problem for handling of damon_stop() failures. wsse and prcl also have a problem in their damon_call() failure handling. As a result, memory leaks, next DAMON operation disruptions, and use-after-free can happen. Fix those.</p> <p>Note that only the damon_start() failure caused issues can reliably be reproduced. Reproducing those issues require the admin permission, though.</p> <p>This patch (of 6):</p> <p>damon_sample_wsse_start() callers assume it will clean up resources when it fails. And the function does the cleanup for context buildup failures. However, it is not doing the cleanup for damon_start() failure. As a result, when damon_start() fails, it leaks the memory for DAMON context. Free the context in case of the failure to fix the issues.</p> <p>Note that the issue can reliably be reproduced because the module calls damon_start() in the exclusive mode. For example,</p> <p>$ sudo damo start $ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid $ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled $ sudo cat /proc/allocinfo | grep damon_new_ctx</p> <p>Because the first command is running another DAMON instance, the third command fails the…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>samples/damon/wsse: handle damon_start() failure</p> <p>Patch series &#34;samples/damon: handle damon_{start,stop}() failures&#34;.</p> <p>All DAMON sample modules are not correctly handling failures from damon_start(). Among those, mtier also has an additional problem for handling of damon_stop() failures. wsse and prcl also have a problem in their damon_call() failure handling. As a result, memory leaks, next DAMON operation disruptions, and use-after-free can happen. Fix those.</p> <p>Note that only the damon_start() failure caused issues can reliably be reproduced. Reproducing those issues require the admin permission, though.</p> <p>This patch (of 6):</p> <p>damon_sample_wsse_start() callers assume it will clean up resources when it fails. And the function does the cleanup for context buildup failures. However, it is not doing the cleanup for damon_start() failure. As a result, when damon_start() fails, it leaks the memory for DAMON context. Free the context in case of the failure to fix the issues.</p> <p>Note that the issue can reliably be reproduced because the module calls damon_start() in the exclusive mode. For example,</p> <p>$ sudo damo start $ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid $ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled $ sudo cat /proc/allocinfo | grep damon_new_ctx</p> <p>Because the first command is running another DAMON instance, the third command fails the…</p> https://vulnerability.circl.lu/vuln/cve-2026-90005