CVE-2023-53276
Last modified
CVE-2023-53276 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | 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.5, < 5.10.180 |
| Linux | Linux Kernel | >= 5.11, < 5.15.111 |
| Linux | Linux Kernel | >= 5.16, < 6.1.28 |
| Linux | Linux Kernel | >= 6.2, < 6.2.15 |
| Linux | Linux Kernel | >= 6.3, < 6.3.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-53276?
How severe is CVE-2023-53276?
How do I fix CVE-2023-53276?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53270In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53271In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53272In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-53273In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53274In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53275In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53277In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53278In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53279In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5328A vulnerability classified as critical has been found in SAT…8.8
- CVE-2023-53280In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53281In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53276?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
