libcrux-ml-dsa: Signature Verification on AVX2 Platforms Mishandles Edge Case
Priority LOW 38CWE-347Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-347.
Summary
The AVX2 implementation of ML-DSA verification incorrectly implemented the `use_hint` function, mishandling an edge case that should lead to signature rejection. ## Impact An attacker could make the ML-DSA verifier accept a crafted invalid signature under a maliciously generated verification key, if the AVX2 implementation is used. ## Mitigation From version `0.0.9` the edge case is handled correctly and invalid signatures are rejected.
Why it matters now
Fix Fixed libcrux-ml-dsa (crates.io): 0.0.9
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | libcrux-ml-dsa (crates.io) | before 0.0.9 | 0.0.9 | Patch available | GHSA-fhvh-vw7h-9xf3 |
- libcrux-ml-dsa (crates.io) Vendor— Affected before 0.0.9 Fixed in 0.0.9 Patch available GHSA-fhvh-vw7h-9xf3
Remediation
- Fix · GHSA-fhvh-vw7h-9xf3 libcrux-ml-dsa (crates.io) Fixed in 0.0.9 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-fhvh-vw7h-9xf3
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences