céu limpo
- [USD] USD 64,517.29
- [BRL] BRL 332,509.19 [USD] USD 64,517.29 [GBP] GBP 48,711.00 [EUR] EUR 56,436.17
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.
[22/06/2026 11:32] Primeiro-ministro do Reino Unido, Keir Starmer, renuncia ao cargo - BBC
[22/06/2026 05:01] 'Todos envolvidos no escândalo Master terão que se explicar', diz presidente do PT - Valor Econômico
[22/06/2026 00:21] Direita prepara terreno para superar esquerda na América do Sul - Poder360
[22/06/2026 09:10] Cubanos superaram venezuelanos em pedidos de refúgio no Brasil em 2025 - G1
[22/06/2026 10:07] Criança de 7 anos morre após ser baleada na cabeça em Nova Iguaçu - G1
[22/06/2026 12:10] Ipsos-Ipec: 38% avaliam governo Lula como ruim ou péssimo, 32% como ótimo ou bom e 28% como regular - G1
[22/06/2026 14:15] Governo nomeia "Fulano" e "Cicrano de tal" como assistentes do GSI de Lula - CNN Brasil
[22/06/2026 11:13] Flávio comemora vitória de Arthur Henrique em Roraima - Poder360
[22/06/2026 08:48] Defesa de Bolsonaro pede a Moraes mais tempo para reuniões antes de depoimento - Revista Oeste
[22/06/2026 08:04] Entenda como esquema internacional usava madeira para esconder cocaína; carga pode ser a maior da história do Brasil - G1