Dislocker through 0.7.3 contains a heap out-of-bounds read vulnerability in get_dataset() and get_next_datum() that never validate dataset and datum sizes against the metadata allocation. Attackers can craft a BitLocker volume image with inflated dataset or datum sizes that, when opened or mounted, crashes dislocker or discloses adjacent heap memory.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 6.9NVD modified 2026-10-10 04:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/Aorimn/dislocker
- https://github.com/Aorimn/dislocker/blob/v0.7.3/src/metadata/datums.c#L589-L640
- https://github.com/Aorimn/dislocker/blob/v0.7.3/src/metadata/metadata.c#L764-L790
- https://github.com/Aorimn/dislocker/commit/9158e9e41dd669b360cbc53cc18ccae729b67b48
- https://www.vulncheck.com/advisories/dislocker-through-0.7.3-heap-out-of-bounds-read-via-bitlocker-metadata-dataset-size