https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 03:43:51 +0000 https://vulnerability.circl.lu/vuln/cve-2023-53396 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ubifs: Fix memory leak in do_rename</p> <p>If renaming a file in an encrypted directory, function fscrypt_setup_filename allocates memory for a file name. This name is never used, and before returning to the caller the memory for it is not freed.</p> <p>When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program &#39;rename&#39; that renames a file in an encrypted directory:</p> <p>unreferenced object 0xffff888101502840 (size 32): comm &#34;rename&#34;, pid 9404, jiffies 4302582475 (age 435.735s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename do_rename ubifs_rename vfs_rename do_renameat2</p> <p>To fix this we can remove the call to fscrypt_setup_filename as it&#39;s not needed.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ubifs: Fix memory leak in do_rename</p> <p>If renaming a file in an encrypted directory, function fscrypt_setup_filename allocates memory for a file name. This name is never used, and before returning to the caller the memory for it is not freed.</p> <p>When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program &#39;rename&#39; that renames a file in an encrypted directory:</p> <p>unreferenced object 0xffff888101502840 (size 32): comm &#34;rename&#34;, pid 9404, jiffies 4302582475 (age 435.735s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename do_rename ubifs_rename vfs_rename do_renameat2</p> <p>To fix this we can remove the call to fscrypt_setup_filename as it&#39;s not needed.</p> https://vulnerability.circl.lu/vuln/cve-2023-53396