Kernel invalid read via UDF length overflow
Published Nov 7, 2024 · Updated Aug 5, 2026
Use of uninitialized data in the Linux kernel UDF filesystem allows local users to trigger an invalid read via a malformed UDF image. udf_current_aext computes an allocation-descriptor length without rejecting overflow, and udf_get_fileshortad later consumes uninitialized data. Triggering requires kernel processing of the crafted filesystem image; the demonstrated result is a KMSAN-detected invalid read, not proven code execution.
Summary
What happened
Use of uninitialized data in the Linux kernel UDF filesystem allows local users to trigger an invalid read via a malformed UDF image. udf_current_aext computes an allocation-descriptor length without rejecting overflow, and udf_get_fileshortad later consumes uninitialized data. Triggering requires kernel processing of the crafted filesystem image; the demonstrated result is a KMSAN-detected invalid read, not proven code execution.
The record
- CVE
- CVE-2024-50143
- Published
- Nov 7, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 7, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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 <0ce61b1f6b32df822b59c680cbe8e5ba5d335742
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1ac49babc952f48d82676979b20885e480e69be8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <264db9d666ad9a35075cc9ed9ec09d021580fbb1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <417bd613bdbe791549f7687bb1b9b8012ff111c2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4fc0d8660e391dcd8dde23c44d702be1f6846c61
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5eb76fb98b3335aa5cca6a7db2e659561c79c32b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <72e445df65a0aa9066c6fe2b8736ba2fcca6dac7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e52e0b92ed31dc62afbda15c243dcee0bb5bb58d
- Affected versionversion=2.6.12
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
- syzkaller C reproducer for the UDF faultproof of concept · demonstrated
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