https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 11:31:19 +0000 https://vulnerability.circl.lu/vuln/cve-2025-38411 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfs: Fix double put of request</p> <p>If a netfs request finishes during the pause loop, it will have the ref that belongs to the IN_PROGRESS flag removed at that point - however, if it then goes to the final wait loop, that will *also* put the ref because it sees that the IN_PROGRESS flag is clear and incorrectly assumes that this happened when it called the collector.</p> <p>In fact, since IN_PROGRESS is clear, we shouldn&#39;t call the collector again since it&#39;s done all the cleanup, such as calling -&gt;ki_complete().</p> <p>Fix this by making netfs_collect_in_app() just return, indicating that we&#39;re done if IN_PROGRESS is removed.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfs: Fix double put of request</p> <p>If a netfs request finishes during the pause loop, it will have the ref that belongs to the IN_PROGRESS flag removed at that point - however, if it then goes to the final wait loop, that will *also* put the ref because it sees that the IN_PROGRESS flag is clear and incorrectly assumes that this happened when it called the collector.</p> <p>In fact, since IN_PROGRESS is clear, we shouldn&#39;t call the collector again since it&#39;s done all the cleanup, such as calling -&gt;ki_complete().</p> <p>Fix this by making netfs_collect_in_app() just return, indicating that we&#39;re done if IN_PROGRESS is removed.</p> https://vulnerability.circl.lu/vuln/cve-2025-38411