IT

Tracker / CVE-2023-53276

CVE-2023-53276

Medium 5.5

In the Linux kernel, the following vulnerability has been resolved: ubifs: Free memory for tmpfile name When opening a ubifs tmpfile on an encrypted directory, function fscrypt_setup_filename allocates memory for the name that is to be stored in the directory entry, but after the name has been copied to the directory entry inode, the memory 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 'tmpfile' just opening a tmpfile: unreferenced object 0xffff88810178f380 (size 32): comm "tmpfile", pid 509, jiffies 4294934744 (age 1524.742s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename ubifs_tmpfile vfs_tmpfile path_openat Free this memory after it has been copied to the inode.

Affected products and versions

linux linux_kernel · … → 4.14.315
linux linux_kernel · 4.15 → 4.19.283
linux linux_kernel · 4.20 → 5.4.243
linux linux_kernel · 5.11 → 5.15.111
linux linux_kernel · 5.16 → 6.1.28
linux linux_kernel · 5.5 → 5.10.180
linux linux_kernel · 6.2 → 6.2.15
linux linux_kernel · 6.3 → 6.3.2

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References