https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 22:36:57 +0000 https://vulnerability.circl.lu/vuln/cve-2025-71072 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>shmem: fix recovery on rename failures</p> <p>maple_tree insertions can fail if we are seriously short on memory; simple_offset_rename() does not recover well if it runs into that. The same goes for simple_offset_rename_exchange().</p> <p>Moreover, shmem_whiteout() expects that if it succeeds, the caller will progress to d_move(), i.e. that shmem_rename2() won&#39;t fail past the successful call of shmem_whiteout().</p> <p>Not hard to fix, fortunately - mtree_store() can&#39;t fail if the index we are trying to store into is already present in the tree as a singleton.</p> <p>For simple_offset_rename_exchange() that&#39;s enough - we just need to be careful about the order of operations.</p> <p>For simple_offset_rename() solution is to preinsert the target into the tree for new_dir; the rest can be done without any potentially failing operations.</p> <p>That preinsertion has to be done in shmem_rename2() rather than in simple_offset_rename() itself - otherwise we&#39;d need to deal with the possibility of failure after successful shmem_whiteout().</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>shmem: fix recovery on rename failures</p> <p>maple_tree insertions can fail if we are seriously short on memory; simple_offset_rename() does not recover well if it runs into that. The same goes for simple_offset_rename_exchange().</p> <p>Moreover, shmem_whiteout() expects that if it succeeds, the caller will progress to d_move(), i.e. that shmem_rename2() won&#39;t fail past the successful call of shmem_whiteout().</p> <p>Not hard to fix, fortunately - mtree_store() can&#39;t fail if the index we are trying to store into is already present in the tree as a singleton.</p> <p>For simple_offset_rename_exchange() that&#39;s enough - we just need to be careful about the order of operations.</p> <p>For simple_offset_rename() solution is to preinsert the target into the tree for new_dir; the rest can be done without any potentially failing operations.</p> <p>That preinsertion has to be done in shmem_rename2() rather than in simple_offset_rename() itself - otherwise we&#39;d need to deal with the possibility of failure after successful shmem_whiteout().</p> https://vulnerability.circl.lu/vuln/cve-2025-71072