Fellipe Weno

fweno.onefour.com.br

Current Conditions

São Paulo
céu limpo

14 ℃

88%

Temperatura

Umidade

Fonte: OpenWeatherMap. - 02:00:01

[USD] USD 79,407.22

[BRL] BRL 399,124.49 [USD] USD 79,407.22 [GBP] GBP 58,689.79 [EUR] EUR 67,779.94
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 of CScriptCheck functors. Each CScriptCheck holds a pointer to a PrecomputedTransactionData object 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 the PrecomputedTransactionData outlives the CScriptCheck.
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 of PrecomputedTransactionData is destroyed before the CCheckQueueControl.
This is not an issue when the block is valid, as CCheckQueueControl::Wait() will be called before the function returns and the PrecomputedTransactionData gets 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.

dog - 02:13:15 up 236 days, 10:44, 3 users, load average: 0.00, 0.00, 0.00

[13/05/2026 21:49] Natália Portinari: Master investiu R$ 614 mi em grupo que financiou filme de Bolsonaro - UOL Notícias

[13/05/2026 18:54] Justiça manda soltar MC Poze do Rodo - G1

[13/05/2026 19:54] Motta não conhece a vida real, diz Skaf, da Fiesp, após acordo para votar projeto da escala 6x1 - Folha de S.Paulo

[13/05/2026 08:04] Indústria de SP pede que Congresso "devolva" MP que zera taxa das blusinhas - CNN Brasil

[13/05/2026 17:20] A 1ª pesquisa eleitoral após a divulgação do áudio de Flávio Bolsonaro a Vorcaro - CartaCapital

[13/05/2026 15:06] Cármen Lúcia anuncia saída do TSE - CNN Brasil

[13/05/2026 23:06] 'Teremos um futuro fantástico juntos', diz Trump em encontro com Xi Jinping em Pequim, com Irã, Taiwan e comércio em pauta - O GLOBO

[13/05/2026 17:12] Vance diz que EUA estão "fazendo progressos" nas negociações com Irã - CNN Brasil

[13/05/2026 17:09] Promotoria pede prisão de candidato da esquerda no Peru no dia em que ele avança ao 2º turno - G1

[13/05/2026 17:49] Papa Leão XIV ameaça excomungar grupo católico ultratradicionalista - Jovem Pan

[CVE-2025-68955] [Modified: 15-01-2026] [Analyzed] [V3.1 S8.0:HIGH] Multi-thread race condition vulnerability in the card framework module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68956] [Modified: 15-01-2026] [Analyzed] [V3.1 S8.0:HIGH] Multi-thread race condition vulnerability in the card framework module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68957] [Modified: 15-01-2026] [Analyzed] [V3.1 S8.4:HIGH] Multi-thread race condition vulnerability in the card framework module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68958] [Modified: 15-01-2026] [Analyzed] [V3.1 S8.0:HIGH] Multi-thread race condition vulnerability in the card framework module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68959] [Modified: 15-01-2026] [Analyzed] [V3.1 S6.2:MEDIUM] Permission verification bypass vulnerability in the media library module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

[CVE-2025-68960] [Modified: 15-01-2026] [Analyzed] [V3.1 S8.4:HIGH] Multi-thread race condition vulnerability in the video framework module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68961] [Modified: 15-01-2026] [Analyzed] [V3.1 S5.1:MEDIUM] Multi-thread race condition vulnerability in the camera framework module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68962] [Modified: 15-01-2026] [Analyzed] [V3.1 S5.1:MEDIUM] Multi-thread race condition vulnerability in the camera framework module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68963] [Modified: 15-01-2026] [Analyzed] [V3.1 S5.7:MEDIUM] Man-in-the-middle attack vulnerability in the Clone module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

[CVE-2025-68964] [Modified: 15-01-2026] [Analyzed] [V3.1 S6.2:MEDIUM] Data verification vulnerability in the HiView module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68965] [Modified: 15-01-2026] [Analyzed] [V3.1 S4.7:MEDIUM] Permission control vulnerability in the Notepad module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

[CVE-2025-68966] [Modified: 15-01-2026] [Analyzed] [V3.1 S5.1:MEDIUM] Permission control vulnerability in the Notepad module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

[CVE-2025-68967] [Modified: 15-01-2026] [Analyzed] [V3.1 S5.7:MEDIUM] Vulnerability of improper permission control in the print module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

[CVE-2025-68968] [Modified: 15-01-2026] [Analyzed] [V3.1 S7.8:HIGH] Double free vulnerability in the multi-mode input module. Impact: Successful exploitation of this vulnerability may affect the input function.

[CVE-2025-68969] [Modified: 15-01-2026] [Analyzed] [V3.1 S6.8:MEDIUM] Multi-thread race condition vulnerability in the thermal management module. Impact: Successful exploitation of this vulnerability may affect availability.

[CVE-2025-68970] [Modified: 15-01-2026] [Analyzed] [V3.1 S6.1:MEDIUM] Permission verification bypass vulnerability in the media library module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

[CVE-2025-0647] [Modified: 26-01-2026] [Analyzed] [V3.1 S7.9:HIGH] In certain Arm CPUs, a CPP RCTX instruction executed on one Processing Element (PE) may inhibit TLB invalidation when a TLBI is issued to the PE, either by the same PE or another PE in the shareability domain. In this case, the PE may retain stale TLB entries which should have been invalidated by the TLBI.

[CVE-2025-66169] [Modified: 16-01-2026] [Analyzed] [V3.1 S5.3:MEDIUM] Cypher Injection vulnerability in Apache Camel camel-neo4j component. This issue affects Apache Camel: from 4.10.0 before 4.10.8, from 4.14.0 before 4.14.3, from 4.15.0 before 4.17.0 Users are recommended to upgrade to version 4.10.8 for 4.10.x LTS and 4.14.3 for 4.14.x LTS and 4.17.0.

[CVE-2025-56226] [Modified: 21-01-2026] [Analyzed] [V3.1 S5.3:MEDIUM] Libsndfile <=1.2.2 contains a memory leak vulnerability in the mpeg_l3_encoder_init() function within the mpeg_l3_encode.c file.

[CVE-2025-71102] [Modified: 25-03-2026] [Analyzed] [V3.1 S5.5:MEDIUM] In the Linux kernel, the following vulnerability has been resolved: scs: fix a wrong parameter in __scs_magic __scs_magic() needs a 'void *' variable, but a 'struct task_struct *' is given. 'task_scs(tsk)' is the starting address of the task's shadow call stack, and '__scs_magic(task_scs(tsk))' is the end address of the task's shadow call stack. Here should be '__scs_magic(task_scs(tsk))'. The user-visible effect of this bug is that when CONFIG_DEBUG_STACK_USAGE is enabled, the shadow call stack usage checking function (scs_check_usage) would scan an incorrect memory range. This could lead 1. **Inaccurate stack usage reporting**: The function would calculate wrong usage statistics for the shadow call stack, potentially showing incorrect value in kmsg. 2. **Potential kernel crash**: If the value of __scs_magic(tsk)is greater than that of __scs_magic(task_scs(tsk)), the for loop may access unmapped memory, potentially causing a kernel panic. However, this scenario is unlikely because task_struct is allocated via the slab allocator (which typically returns lower addresses), while the shadow call stack returned by task_scs(tsk) is allocated via vmalloc(which typically returns higher addresses). However, since this is purely a debugging feature (CONFIG_DEBUG_STACK_USAGE), normal production systems should be not unaffected. The bug only impacts developers and testers who are actively debugging stack usage with this configuration enabled.