Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Aorimn | dislocker | ≤ 0.7.3 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | dislocker | 0.7.4-1 | — |
| Debian 13 | dislocker | No fix yet | — |
| Debian 12 | dislocker | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | dislocker | No fix yet | — |
| Ubuntu 26.04 LTS | dislocker | No fix yet | — |
| Ubuntu 24.04 LTS | dislocker | No fix yet | — |
| Ubuntu 22.04 LTS | dislocker | No fix yet | — |
| Ubuntu 20.04 LTS | dislocker | No fix yet | — |
Show 1 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 18.04 LTS | dislocker | No fix yet | — |
References
- Patch Commit patch
- https://github.com/Aorimn/dislocker/blob/v0.7.3/src/metadata/metadata.c#L764-L790 technical-description
- https://github.com/Aorimn/dislocker/blob/v0.7.3/src/metadata/datums.c#L589-L640 technical-description
- https://github.com/Aorimn/dislocker product
- VulnCheck Advisory: Dislocker through 0.7.3 Heap Out-of-Bounds Read via BitLocker Metadata Dataset Size third-party-advisory