CVE-2025-46597 - Highly unlikely remote crash on 32-bit systems

Headline:
CVE-2025-46597 - Highly unlikely remote crash on 32-bit systems

Summary:
This lead was identified from Bitcoin Core Blog. It has been saved for accountability coverage and should be reviewed against the original source before expansion.

What the record says:
The source headline is: CVE-2025-46597 - Highly unlikely remote crash on 32-bit systems. The source summary says: Disclosure of the details of a bug on 32-bit systems which may, in a rare edge case, cause the node to crash when receiving a pathological block. This bug would be extremely hard to exploit. A fix was released on October 10th 2025 in Bitcoin Core v30.0. This issue is considered Low severity. Details Before writing a block to disk, Bitcoin Core checks that its size is within a normal range. This check would overflow on 32-bit systems for blocks over 1GB, and make the node crash when writing it to disk. Such a block cannot be sent using the BLOCK message, but could in theory be sent as a compact block if the victim node has a non-default large mempool which already contains 1GB of transactions. This would require the victim to have set their -maxmempool option to a value greater than 3GB, while 32-bit systems may have at most 4GiB of memory. This issue was indirectly prevented by capping t

Why it matters:
This may be relevant to public accountability, consumer protection, government oversight, fraud monitoring, or financial transparency depending on the source record.

What is not yet proven:
This draft should not be treated as proof beyond what the linked source directly supports. Avoid adding accusations, private information, or copied text from the original source.

Source:
https://bitcoincore.org/en/2025/10/24/disclose-cve-2025-46597/

AI writer note: OPENAI_API_KEY is empty, so this was generated with the built-in safe fallback writer.