céu limpo
- [USD] USD 62,171.61
- [BRL] BRL 321,899.71 [USD] USD 62,171.61 [GBP] GBP 46,429.63 [EUR] EUR 53,961.16
Price index provided by blockchain.info. - After Bitcoin Core 0.14.0 and before Bitcoin Core 29.0, validating a specially-crafted block may cause the node to access previously freed memory.
During validation, necessary data required for checking inputs for each transaction is pre-calculated and cached. For specially crafted invalid blocks, it was possible for this data to be destroyed while it was still being accessed by a background validation thread. An attacker capable of mining a block with sufficient proof-of-work could have exploited this to crash victim nodes. Because of the nature of use-after-free bugs, it is possible that the crash could have been used for remote code execution, though constraints on the input (block) data make this unlikely.
This issue is considered High severity.
Details
By default, script validation for new blocks is dispatched to background threads via a vector ofCScriptCheckfunctors. Each CScriptCheck holds a pointer to aPrecomputedTransactionDataobject which stores some data needed by each input in the transaction. Because it stores a pointer and not the data itself, care must be taken to ensure that thePrecomputedTransactionDataoutlives theCScriptCheck.
The script checks lifetime is enforced by an RAII class,CCheckQueueControl. However, the control is intantiated before the precomputed transaction data. Because local objects in C++ are destructed in reverse order of construction, this means the vector ofPrecomputedTransactionDatais destroyed before theCCheckQueueControl.
This is not an issue when the block is valid, asCCheckQueueControl::Wait()will be called before the function returns and thePrecomputedTransactionDatagets destroyed. However, in case of an early return (when a separate check fails) a background script thread may read the precomputed transaction data after it was destroyed. An attacker could exploit this to crash victim nodes at the expense of a valid PoW at tip.
Attribution
Cory Fields (MIT DCI) discovered this vulnerability and responsibly disclosed it in a detailed report containing a proof of concept for reproduction and a proposed mitigation.
Timeline
- 2024-11-02 Cory Fields privately reports the bug
- 2024-11-06 Pieter Wuille pushes a covert fix to already open PR #31112 which works around the issue by removing the early returns
- 2024-12-03 PR #31112 is merged
- 2025-04-12 Bitcoin Core version 29.0 is released with a fix
- 2026-04-19 The last vulnerable Bitcoin Core version (28.x) goes end of life
- 2026-05-05 Public disclosure.
[07/06/2026 13:31] Quem é Éderson, volante que foi convocado para substituir Wesley na seleção brasileira - O Globo
[07/06/2026 12:19] Fábio Giga estava com influencer Bitelo no momento em que colidiu Porsche - CNN Brasil
[06/06/2026 10:04] Candidato da esquerda à Presidência do Peru é enviado a julgamento às vésperas do 2º turno - CartaCapital
[07/06/2026 06:03] Zelensky: ataque à instalação de combustível nuclear é "extremamente vil" - CNN Brasil
[07/06/2026 06:01] PCC e CV estão presentes em mais Estados do que o McDonald’s - Poder360
[06/06/2026 23:51] CNJ descobre salários de mais de R$ 1 milhão por mês a juízes - Revista Oeste
[07/06/2026 08:37] BH registra segundo dia mais frio de 2026 e Defesa Civil - O TEMPO
[06/06/2026 03:34] Parada LGBT+ em SP terá segurança reforçada com mais de 1,5 mil policiais - CNN Brasil
[06/06/2026 12:56] PF quer acionar Interpol para rastrear R$ 60 mi enviados por Vorcaro aos EUA - Revista Oeste
[06/06/2026 14:01] UE oficializa veto à compra de carne do Brasil a partir de setembro - Poder360