CVE-2024-50143: udf: fix uninit-value use in udf_get_fileshortad
In the Linux kernel, the following vulnerability has been resolved:
udf: fix uninit-value use in udf_get_fileshortad
Check for overflow when computing alen in udf_current_aext to mitigate
later uninit-value use in udf_get_fileshortad KMSAN bug[1].
After applying the patch reproducer did not trigger any issue[2].
[1] https://syzkaller.appspot.com/bug?extid=8901c4560b7ab5c2f9df
[2] https://syzkaller.appspot.com/x/log.txt?x=10242227980000
Security readout for executives and security teams
Plain-English summary
A flaw in Linux UDF filesystem handling can use uninitialized data after an overflow calculation. Exploitation requires local access and user interaction, but the assigned CVSS score indicates potentially serious confidentiality, integrity, and availability impact. The public evidence shows a syzkaller-discovered kernel bug, not attacks in the wild.
Executive priority
Treat this as a high-severity patching item, especially for shared systems or environments processing untrusted media. It does not currently justify an exploitation-driven emergency response because the supplied sources show no active attacks. Require owners to establish exposure, apply supported kernel updates, and verify the running kernel within the normal high-severity remediation window.
Technical view
An overflow while calculating alen in udf_current_aext can lead udf_get_fileshortad to consume an uninitialized value. The upstream fix adds overflow checking, and the cited reproducer stopped triggering the KMSAN finding after patching. The supplied record assigns CVSS 3.1 score 7.8 and CWE-908.
Likely exposure
Exposure is most plausible on affected Linux systems that process UDF filesystems, including systems where users can interact with relevant media or images. The CVSS vector is local, requires user interaction, and requires no privileges. Exact exposure depends on the running kernel, distribution backports, and whether UDF processing is reachable.
Exploitation context
The supplied record is not in KEV and provides no evidence of active exploitation. Public evidence documents automated syzkaller discovery and a reproducer used to confirm the fix. Although CVSS estimates high potential impact, the bundle does not establish demonstrated compromise, reliable exploitation, or specific real-world outcomes.
Researcher notes
The affected-version data mixes kernel versions with repeated commit identifiers, so it should not be interpreted as a complete distribution-level boundary. Multiple stable-branch commits are cited. The bundle confirms an overflow check prevents the KMSAN reproducer, but it does not document exploit reliability, attacker-controlled effects, or concrete post-trigger behavior.
Mitigation direction
Upgrade to a vendor-supported kernel package containing the applicable upstream stable fix.
Check distribution guidance because package versions and backported fixes may differ from upstream kernel versions.
Prioritize systems that permit users to process UDF media or filesystem images.
Apply temporary access restrictions around untrusted UDF content where patching must be delayed.
Reboot after upgrading and confirm the patched kernel is actually running.
Validation and detection
Inventory running kernel and distribution package versions across Linux systems.
Compare each package against vendor advisories and documented backports for CVE-2024-50143.
Identify systems where UDF filesystem processing is enabled or operationally reachable.
Confirm the running kernel contains the applicable stable fix, not merely an installed update.
Use controlled regression testing or vendor validation to confirm remediation without exposing production systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-908: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
2ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-908 · source CWE mapping
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.