nuvens dispersas
- [USD] USD 63,985.01
- [BRL] BRL 329,625.20 [USD] USD 63,985.01 [GBP] GBP 48,212.32 [EUR] EUR 55,772.54
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.
[20/06/2026 14:13] Lula tem 47% contra 43% de Flávio no 2º turno, diz Datafolha - Poder360
[20/06/2026 18:35] Irã alerta navios contra tentativas de atravessar o Estreito de Ormuz - CNN Brasil
[20/06/2026 14:54] 'Alerta extremo' da Defesa Civil é o aviso mais grave do sistema e já foi usado em outras situações de risco - G1
[20/06/2026 21:12] Zema cita Taylor Swift em vídeo contra Lula e Wagner - Poder360
[20/06/2026 19:45] Onda de frio ganha força e pode levar neve ao Sul do Brasil nesta semana - CNN Brasil
[20/06/2026 21:00] Tunísia x Japão: onde assistir ao vivo, horário, palpite e escalações do jogo da Copa do Mundo - ND Mais
[20/06/2026 11:48] Cacique Raoni embarca em avião do Mato Grosso direto a hospital em São Paulo para continuidade do tratamento - AEROIN
[19/06/2026 16:27] MEC usará Enamed como exame obrigatório para exercício da medicina - CNN Brasil
[20/06/2026 14:30] Líder do Vox chama Moraes de 'delinquente' e diz que Eduardo sofreu 'golpe judicial' - Revista Oeste
[20/06/2026 10:26] Polícia prende três suspeitos de ocultar provas após morte de jovem lançada sem cordas em rope jump - G1