You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ntfs_dent.cpp -> ntfs_proc_idxentry: In the sanity check, the code returns without freeing fs_name.
ntfs_dent.cpp -> ntfs_find_file: fs_file is not freed in case tsk_fs_name_alloc fails.
fatxxfs_dent.c -> fat_xxfs_dent_parse_buf: There are 2 returns from the function without fs_name being freed.
fs_dir.c -> tsk_fs_dir_get: 2 returns where fs_file->name and fs_file is not freed.
I just did a quick look at references to tsk_fs_name_alloc and found all this potential memory leaks.
Do you use any code analysis tool?
The text was updated successfully, but these errors were encountered:
ntfs_dent.cpp -> ntfs_proc_idxentry: In the sanity check, the code returns without freeing fs_name.
ntfs_dent.cpp -> ntfs_find_file: fs_file is not freed in case tsk_fs_name_alloc fails.
fatxxfs_dent.c -> fat_xxfs_dent_parse_buf: There are 2 returns from the function without fs_name being freed.
fs_dir.c -> tsk_fs_dir_get: 2 returns where fs_file->name and fs_file is not freed.
I just did a quick look at references to tsk_fs_name_alloc and found all this potential memory leaks.
Do you use any code analysis tool?
The text was updated successfully, but these errors were encountered: