Spurious filename hash via uninitialized buffer read
Published Sep 15, 2025 · Updated Sep 15, 2025
Uninitialized memory use in Linux kernel UDF filename conversion allows local users to generate spurious hashes via crafted names. In udf_name_from_CS0, a length check permits zero-length output before reading str_o[0], so the conversion logic consults an uninitialized buffer byte when deciding whether a CRC-based unification hash is needed. The path requires processing a UDF name beginning with a period and measuring two through five characters; the reported practical consequence is an unnecessary filename prefix, not data disclosure or corruption.
Summary
What happened
Uninitialized memory use in Linux kernel UDF filename conversion allows local users to generate spurious hashes via crafted names. In udf_name_from_CS0, a length check permits zero-length output before reading str_o[0], so the conversion logic consults an uninitialized buffer byte when deciding whether a CRC-based unification hash is needed. The path requires processing a UDF name beginning with a period and measuring two through five characters; the reported practical consequence is an unnecessary filename prefix, not data disclosure or corruption.
The record
- CVE
- CVE-2023-53165
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <008ae78d1e12efa904dc819b1ec83e2bca6b2c56
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <028f6055c912588e6f72722d89c30b401bbcf013
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3f1368af47acf4d0b2a5fb0d2c0d6919d2234b6d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4503f6fc95d6dee85fb2c54785848799e192c51c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4d50988da0db167aed6f38685145cb5cd526c4f8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <985f9666698960dfc87a106d6314203fa90fda75
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a6824149809395dfbb5bc36bc7057cc3cb84e56d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b37f998d357102e8eb0f8eeb33f03fff22e49cbf
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo