CVE-2023-53276

ubifs: Free memory for tmpfile name

MEDIUM

5.5

CVSS Score

Published: September 16, 2025 at 08:11 AM UTC

Updated: June 17, 2026 at 06:44 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 4.14.3154.10 ≤ v < 4.14.3154.10 ≤ v < 4.19.2834.10 ≤ v < 5.10.1804.10 ≤ v < 5.15.1114.10 ≤ v < 5.4.2434.10 ≤ v < 6.1.284.10 ≤ v < 6.2.154.10 ≤ v < 6.3.24.10 ≤ v < 6.44.15 ≤ v < 4.19.2834.20 ≤ v < 5.4.2435.11 ≤ v < 5.15.1115.16 ≤ v < 6.1.285.5 ≤ v < 5.10.1806.2 ≤ v < 6.2.156.3 ≤ v < 6.3.24.10f4f61d2cc6d8789a52245a4733b3e5643be154f3

Vendor states this is fixed in 107d481642c356a5668058066360fc473911e628 (fixed)

Vendor states this is fixed in 1e43d4284bdc3bd34bd770fea13910ac37ab0618 (fixed)

Vendor states this is fixed in 1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3 (fixed)

Vendor states this is fixed in 29738e1bcc799dd754711d4e4aab967f0c018175 (fixed)

Vendor states this is fixed in 823f554747f8aafaa965fb2f3ae794110ed429ef (fixed)

Vendor states this is fixed in 8ad8c67a897e68426e85990ebfe0a7d1f71fc79f (fixed)

Vendor states this is fixed in b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3 (fixed)

Vendor states this is fixed in ce840284929b75dbbf062e0ce7fcb78a63b08b5e (fixed)

Vendor states this is fixed in fd197308c0e4f738c7ea687d5332035c5753881c (fixed)

Vendor states this is fixed in 4.10 (unaffected)

Vendor states this is fixed in 4.14.315 (unaffected)

Vendor states this is fixed in 4.19.283 (unaffected)

Vendor states this is fixed in 5.10.180 (unaffected)

Vendor states this is fixed in 5.15.111 (unaffected)

Vendor states this is fixed in 5.4.243 (unaffected)

Vendor states this is fixed in 6.1.28 (unaffected)

Vendor states this is fixed in 6.2.15 (unaffected)

Vendor states this is fixed in 6.3.2 (unaffected)

Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references