CVE-2023-53165
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-11-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-908 | The product uses or accesses a resource that has not been initialized. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is in the Linux kernel's UDF filesystem code. It involves uninitialized array access when handling certain filenames that start with a dot (.) and are between 2 and 5 characters long. Specifically, the UDF charset conversion code reads uninitialized memory in the output buffer, which can cause the filename to be incorrectly modified by prepending a "unification hash" even when it is not needed. The issue has been fixed.
How can this vulnerability impact me? :
The practical impact of this vulnerability is limited to the possibility that filenames may be incorrectly modified by having a "unification hash" prepended when it is not actually needed. There is no indication of further security impact such as data corruption, privilege escalation, or information disclosure.