Description
In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memory leak in do_rename 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. When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program 'rename' that renames a file in an encrypted directory: unreferenced object 0xffff888101502840 (size 32): comm "rename", pid 9404, jiffies 4302582475 (age 435.735s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename do_rename ubifs_rename vfs_rename do_renameat2 To fix this we can remove the call to fscrypt_setup_filename as it's not needed.
Product status
c67bc98d1f0853bb196e9c48eab38b6f2ddab795 (git) before 43b2f7d690697182beed6f71aa57b7249d3cfc9c
278d9a243635f26c05ad95dcf9c5a593b9e04dc6 (git) before 9f565752b328fe53c9e42b7d4e4d89a1da63d738
278d9a243635f26c05ad95dcf9c5a593b9e04dc6 (git) before 7e264f67b7d6580eff5c2696961039fd05c69258
278d9a243635f26c05ad95dcf9c5a593b9e04dc6 (git) before 517ddc0259d7a7231486bdafde8035c478bc4088
278d9a243635f26c05ad95dcf9c5a593b9e04dc6 (git) before 3a36d20e012903f45714df2731261fdefac900cb
17495eb2f7f08113b50aba298c2c1a045824c4f7 (git)
868de33a39e0e1e91ed3ce4a23a65f30144d2443 (git)
5.18
Any version before 5.18
5.15.112 (semver)
6.1.28 (semver)
6.2.15 (semver)
6.3.2 (semver)
6.4 (original_commit_for_fix)
References
git.kernel.org/...c/43b2f7d690697182beed6f71aa57b7249d3cfc9c
git.kernel.org/...c/9f565752b328fe53c9e42b7d4e4d89a1da63d738
git.kernel.org/...c/7e264f67b7d6580eff5c2696961039fd05c69258
git.kernel.org/...c/517ddc0259d7a7231486bdafde8035c478bc4088
git.kernel.org/...c/3a36d20e012903f45714df2731261fdefac900cb
