Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-53396

ubifs: Fix memory leak in do_rename

Medium5.5EPSS 0.15%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memory leak in do_rename If renaming a file in an encrypted directory, function fscrypt_setup_filename allocates memory for a file name. This name is never used, and before returning to the caller the memory for it 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 'rename' that renames a file in an encrypted directory: unreferenced object 0xffff888101502840 (size 32): comm "rename", pid 9404, jiffies 4302582475 (age 435.735s) backtrace: __kmem_cache_alloc_node __kmalloc fscrypt_setup_filename do_rename ubifs_rename vfs_rename do_renameat2 To fix this we can remove the call to fscrypt_setup_filename as it's not needed.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53396, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected c67bc98d1f0853bb196e9c48eab38b6f2ddab795 – < 43b2f7d690697182beed6f71aa57b7249d3cfc9c
    • affected 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 – < 9f565752b328fe53c9e42b7d4e4d89a1da63d738
    • affected 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 – < 7e264f67b7d6580eff5c2696961039fd05c69258
    • affected 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 – < 517ddc0259d7a7231486bdafde8035c478bc4088
    • affected 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 – < 3a36d20e012903f45714df2731261fdefac900cb
    • affected 17495eb2f7f08113b50aba298c2c1a045824c4f7
    • affected 868de33a39e0e1e91ed3ce4a23a65f30144d2443
    • affected 5.15.33 – < 5.15.112
    • affected 5.16.19 – < 5.17
    • affected 5.17.2 – < 5.18
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 5.15.112 – ≤ 5.15.*
    • unaffected 6.1.28 – ≤ 6.1.*
    • unaffected 6.2.15 – ≤ 6.2.*
    • unaffected 6.3.2 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53396 badge
[![CVE-2023-53396](https://trackcve.app/badge/CVE-2023-53396.svg)](https://trackcve.app/cve/CVE-2023-53396)

Record last updated .