https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 02:03:25 +0000 https://vulnerability.circl.lu/vuln/cve-2025-21893 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>keys: Fix UAF in key_put()</p> <p>Once a key&#39;s reference count has been reduced to 0, the garbage collector thread may destroy it at any time and so key_put() is not allowed to touch the key after that point. The most key_put() is normally allowed to do is to touch key_gc_work as that&#39;s a static global variable.</p> <p>However, in an effort to speed up the reclamation of quota, this is now done in key_put() once the key&#39;s usage is reduced to 0 - but now the code is looking at the key after the deadline, which is forbidden.</p> <p>Fix this by using a flag to indicate that a key can be gc&#39;d now rather than looking at the key&#39;s refcount in the garbage collector.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>keys: Fix UAF in key_put()</p> <p>Once a key&#39;s reference count has been reduced to 0, the garbage collector thread may destroy it at any time and so key_put() is not allowed to touch the key after that point. The most key_put() is normally allowed to do is to touch key_gc_work as that&#39;s a static global variable.</p> <p>However, in an effort to speed up the reclamation of quota, this is now done in key_put() once the key&#39;s usage is reduced to 0 - but now the code is looking at the key after the deadline, which is forbidden.</p> <p>Fix this by using a flag to indicate that a key can be gc&#39;d now rather than looking at the key&#39;s refcount in the garbage collector.</p> https://vulnerability.circl.lu/vuln/cve-2025-21893