nublado
- [USD] USD 61,189.92
- [BRL] BRL 317,936.71 [USD] USD 61,189.92 [GBP] GBP 46,516.88 [EUR] EUR 53,986.40
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 06:28] Terremoto na Venezuela provoca mais de 30 mortes, 700 feridos e é sentido no Brasil; o que se sabe - BBC
[25/06/2026 06:30] Operação mira cúpula de empresa de ônibus e vereador de SP por lavagem de dinheiro para o PCC - G1
[25/06/2026 07:15] PF deflagra operação sobre irregularidades nas Americanas - CNN Brasil
[25/06/2026 06:44] Se a ofendi, “peço desculpas", diz Flávio a Michelle - Poder360
[24/06/2026 18:04] Após reunião com Lula, Jaques Wagner deixa liderança no Senado - Correio Braziliense
[24/06/2026 20:05] 'Mulheres em casa': valentia de Bolsonaro desdiz enfermidade - UOL Notícias
[25/06/2026 07:29] PF mira deputado Josimar Maranhãozinho em operação contra corrupção - Metrópoles
[25/06/2026 07:15] Polícia investiga fraude de R$ 1 bilhão envolvendo banco extinto no RJ - CNN Brasil
[24/06/2026 22:52] Prefeito do Rio anuncia ponto facultativo para o próximo jogo do Brasil na Copa, segunda-feira - O Globo
[24/06/2026 18:53] Itamaraty reage à inscrição de Flávio para discursar em audiência sobre tarifaço nos EUA e fala em ‘traidores da pátria’ - O Globo