CVE-2023-53396: ubifs: Fix memory leak in do_rename
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3a36d20e012903f45714df2731261fdefac900cb, 43b2f7d690697182beed6f71aa57b7249d3cfc9c, 5.15.112.
Low priority for now. Upgrade to Linux Linux 3a36d20e012903f45714df2731261fdefac900cb, 43b2f7d690697182beed6f71aa57b7249d3cfc9c, 5.15.112 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15.33 and later · before 5.15.112
- linux linux kernel5.16.19 and later · before 5.17
- linux linux kernel5.17.2 and later · before 6.1.28
- linux linux kernel6.2 and later · before 6.2.15
- linux linux kernel6.3 and later · before 6.3.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 17495eb2f7f08113b50aba298c2c1a045824c4f7, 868de33a39e0e1e91ed3ce4a23a65f30144d2443, 5.18affected
- c67bc98d1f0853bb196e9c48eab38b6f2ddab795 and later · before 43b2f7d690697182beed6f71aa57b7249d3cfc9caffected · git
- 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 and later · before 9f565752b328fe53c9e42b7d4e4d89a1da63d738affected · git
- 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 and later · before 7e264f67b7d6580eff5c2696961039fd05c69258affected · git
- 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 and later · before 517ddc0259d7a7231486bdafde8035c478bc4088affected · git
- 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 and later · before 3a36d20e012903f45714df2731261fdefac900cbaffected · git
- 5.15.33 and later · before 5.15.112affected · semver
- 5.16.19 and later · before 5.17affected · semver
- 5.17.2 and later · before 5.18affected · semver
- before 5.18not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53393Sep 18, 2025 · RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device22Monitor
- ← EarlierCVE-2023-53395Sep 18, 2025 · ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer31Monitor
- Later →CVE-2023-53397Sep 18, 2025 · modpost: fix off by one in is_executable_section()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3a36d20e012903f45714df2731261fdefac900cb | Vendor (CNA) |
| Linux Linux | 43b2f7d690697182beed6f71aa57b7249d3cfc9c | Vendor (CNA) |
| Linux Linux | 5.15.112 | Vendor (CNA) |
| Linux Linux | 5.17 | Vendor (CNA) |
| Linux Linux | 5.18 | Vendor (CNA) |
| Linux Linux | 517ddc0259d7a7231486bdafde8035c478bc4088 | Vendor (CNA) |
| Linux Linux | 7e264f67b7d6580eff5c2696961039fd05c69258 | Vendor (CNA) |
| Linux Linux | 9f565752b328fe53c9e42b7d4e4d89a1da63d738 | Vendor (CNA) |
| debian:linux | 6.1.37-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.