nuvens quebradas
- [USD] USD 62,566.57
- [BRL] BRL 324,926.98 [USD] USD 62,566.57 [GBP] GBP 46,695.62 [EUR] EUR 54,072.10
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.
[09/06/2026 07:40] Mônica Bergamo: PF vai recusar nova delação de Daniel Vorcaro - Folha de S.Paulo
[08/06/2026 23:00] Painel: Senado recusa pedido de retirada de apoio a projeto alternativo ao fim da 6x1 - Folha de S.Paulo
[08/06/2026 21:08] Nunes Marques leva decisão sobre AtlasIntel para julgamento nesta 3ª - Poder360
[09/06/2026 00:04] Peru: resultado da eleição segue indefinido com Sánchez e Keiko Fujimori disputando voto a voto - G1
[08/06/2026 21:08] Janja chama Malafaia de "insignificante" durante evento do PT - Poder360
[09/06/2026 03:37] Vacina contra dengue do Butantan: governo não tem prazo para investigação - CNN Brasil
[09/06/2026 06:10] Carreta com carga de combustível tomba e fecha a BR-381, em Minas - Rádio Itatiaia
[08/06/2026 20:22] Atenção para virada radical de tempo em SP - Climatempo
[08/06/2026 06:15] Governo Lula tenta diálogo com os EUA sobre tarifas nesta semana - Brasil 247
[08/06/2026 07:00] Caso Henry Borel: testemunha relatou agressões atribuídas a Jairinho desde os 5 anos - Extra online