nublado
- [USD] USD 59,224.11
- [BRL] BRL 307,527.09 [USD] USD 59,224.11 [GBP] GBP 44,856.57 [EUR] EUR 52,059.71
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.
[25/06/2026 14:46] Terremotos na Venezuela: Número de mortos sobe para 188 - CNN Brasil
[25/06/2026 12:56] Libras, Estrela de Davi e honrarias: o cenário escolhido por Michelle Bolsonaro em vídeo que critica Flávio - G1
[25/06/2026 10:21] Ponto facultativo? Veja os horários dos jogos do Brasil até uma possível final da Copa - GE
[25/06/2026 12:38] Lula critica “vagabundos profissionais em tentar vender a Petrobras” - Brasil 247
[25/06/2026 15:24] Vereador seria morto pelo PCC por desvio, mas foi 'perdoado', diz polícia - UOL Notícias
[25/06/2026 11:25] Lula anuncia Teresa Leitão como nova líder do governo no Senado - Brasil 247
[25/06/2026 11:07] Sicupira, Saggioro e filho de Lemann: quem são os alvos da PF no caso de fraude nas Americanas - G1
[25/06/2026 14:16] Gonet diz que ainda não há elementos para punir Bolsonaro por caso de arma apreendida - R7
[25/06/2026 09:15] Marília Campos chama de equívoco candidatura petista em MG e descarta se candidatar ao governo - Estadão
[25/06/2026 11:50] SP: Haddad define França como vice; Tebet e Marina vão disputar o Senado - CNN Brasil