céu limpo
- [USD] USD 80,801.96
- [BRL] BRL 396,802.28 [USD] USD 80,801.96 [GBP] GBP 59,667.48 [EUR] EUR 68,811.68
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.
[12/05/2026 12:46] Por que a UE vetou as exportações brasileiras de carne? Entenda - CNN Brasil
[12/05/2026 12:35] Lula destina R$ 330,6 mi para blindar 138 presídios do país - Poder360
[12/05/2026 11:27] Nunes Marques assume presidência do TSE com festa a R$ 800 o convite - Correio Braziliense
[12/05/2026 15:09] Cão Orelha não morreu por agressão de adolescentes, e MP pede arquivamento - UOL Notícias
[12/05/2026 05:55] Explosão atinge casas e deixa um morto em São Paulo - Revista Oeste
[12/05/2026 04:00] Além de triplex, Ciro Nogueira comprou R$ 7 milhões em imóveis em SP após se aliar ao Master - Metrópoles
[12/05/2026 15:27] Carreta desgovernada provoca acidente envolvendo 13 veículos no Anel Rodoviário de BH - O TEMPO
[12/05/2026 07:08] Chuvas: com volume superior a 40 mm, veja onde mais choveu em Pernambuco nesta terça (12) - Folha PE
[12/05/2026 11:51] ‘Pai de pet’, deputado Marcelo Queiroz é investigado por desvio milionário em castração - Jovem Pan
[12/05/2026 08:01] Irã dá ultimato aos Estados Unidos para que aceitem o plano de paz - CartaCapital