Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0212 json

Potentially Incorrect Output of Constant-Time Swap/Select on Aarch64

published 5mo ago modified 3mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

The implementation of constant-time swap and select on aarch64 platforms used a `cmp` instruction in inline assembly to check whether an 8-bit wide selector was 0. The `cmp` instruction works on 32-bit registers, which included the unspecified high 24 bits of the `cmp` operand. Depending on the execution environment the `cmp` could thus potentially return an incorrect result because its operand's high bits in the inline assembly were set when Rust expected them to be unset. This could lead to incorrect results for the constant-time swap and select operations built from this comparison.

## Impact In certain circumstances the swap and select instructions on aarch64 platforms returned incorrect results.

## Mitigation Starting from version `0.0.6`, the selector is compared using a `tst` instruction with a mask, which only compares the first 8 bits of the selector.

Patch / fix

  • crates.io libcrux-secrets 0.0.6

Is RUSTSEC-2026-0212 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io libcrux-secrets
>=0.0.0-0, <0.0.6
0.0.6

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.