1sealsemantic last-mile verification

Research / Finding

reject all negative merkleized-map return values before using their length

F-LEDGER-BTC-NEGRC-002

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

—score not recorded
LedgerHQ/app-bitcoinReported fixLedgerHQ/app-bitcoin

reject all negative merkleized-map return values before using their length

fixed in public source; rollout not reverified
details
Finding IDs
F-LEDGER-BTC-NEGRC-002
Status
fixed in public source; rollout not reverified
Disclosure date
Note
txhashes and sign_psbt callers check < 0 rather than only == -1, preventing other error returns from being used as lengths. Mapping is based on the reported callsites and public diff. Release inclusion and device rollout were not independently checked.

F-LEDGER-BTC-NEGRC-002: Memory safety. A negative return value becomes an unsigned buffer length. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-LEDGER-BTC-NEGRC-002

Security area (1seal assessment): Memory safety. Negative error codes must not cross into unsigned buffer-length operations. Reviewed 23 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.