Service interruption via premature inline length update
Published Sep 16, 2025 · Updated Sep 16, 2025
Improper file-length handling in the Linux kernel UDF driver allows local users to interrupt service through failed inline-file writes. In udf_file_write_iter(), the driver set i_lenAlloc to the requested end position before __generic_file_write_iter() completed, leaving the inline-data length overstated after failed or partial writes. The path requires write access to a mounted UDF filesystem using embedded inode data; the published record does not identify a specific hang or crash mode.
Summary
What happened
Improper file-length handling in the Linux kernel UDF driver allows local users to interrupt service through failed inline-file writes. In udf_file_write_iter(), the driver set i_lenAlloc to the requested end position before __generic_file_write_iter() completed, leaving the inline-data length overstated after failed or partial writes. The path requires write access to a mounted UDF filesystem using embedded inode data; the published record does not identify a specific hang or crash mode.
The record
- CVE
- CVE-2023-53295
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 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 <256fe4162f8b5a1625b8603ca5f7ff79725bfb47
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5621f7a8139053d0c3c47fb68ee9f602139eb40a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5a6c373d761f55635e175fa2f407544bae8f583b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6837910aeb2c9101fc036dcd1b1f32615c20ec1a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d18cedc1ef0caeb1567cab660079e48844ff6d6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7bd8d9e1cf5607ee14407f4060b9a1dbb3c42802
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c5787d77a5c29fffd295d138bd118b334990a567
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <eb2133900cac2d2f78befd6be41666cf1a2315d9
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