céu pouco nublado
- [USD] USD 78,240.09
- [BRL] BRL 397,500.36 [USD] USD 78,240.09 [GBP] GBP 58,701.35 [EUR] EUR 67,291.72
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.
[16/05/2026 12:05] Datafolha 2º turno: Lula e Flávio têm 45% das intenções de voto - G1
[16/05/2026 06:39] Havengate: o fundo na mira da PF que conecta Vorcaro, Flávio e Eduardo Bolsonaro - BBC
[16/05/2026 10:13] Taiwan afirma que é uma nação “independente” após advertência de Trump - Correio do Povo
[16/05/2026 10:53] Tarcísio alega gripe e falta a evento com Flávio Bolsonaro em SP - Metrópoles
[16/05/2026 07:50] Análise: Como a Refit aliançou-se ao Centrão e ao bolsonarismo para lesar o erário - Valor Econômico
[16/05/2026 11:39] Joaquim Barbosa se filia ao DC e deve disputar a Presidência da República - G1
[16/05/2026 12:59] Ciro lança pré-candidatura, fala de 'lealdade', critica 'frouxos' e diz que vai resolver a segurança - Diário do Nordeste
[16/05/2026 10:22] Vídeo: chileno preso por racismo e homofobia imitou macaco em voo da Latam - CNN Brasil
[16/05/2026 12:42] Defesa Civil alerta: SP terá queda nas temperaturas e temporais até segunda-feira (18) - Olhar Digital
[16/05/2026 10:58] Três estados podem ter chuva acima de 100 mm antes da nova massa polar - MetSul Meteorologia