Fix reusing large allocations in generation memory contexts

If an allocation larger than 1 GB is made from a generation memory
context, and the allocation is later freed, don't try to reuse the
block for smaller allocations later.  The problem is that the standard
layout for a MemoryChunk cannot represent cannot represent an offset
larger than 1 GB (MEMORYCHUNK_MAX_BLOCKOFFSET) from the beginning of
the block, so if MemoryChunk is carved from the very end of the larger
block, the offset stored in the memory chunk overflows.  That leads to
memory corruption.

Backpatch to version 15, where the reuse of blocks was introduced,
although the segfault is only reproducable on version 16 onwards.
Version 15 used a custom GenerationChunk struct which didn't have the
overflow risk that the MemoryChunk struct used in later versions has.

Reported-by: Jayden Sarveshkumar <[email protected]>
Reviewed-by: Noah Misch <[email protected]>
Backpatch-through: v15
Security: CVE-2026-116328

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/e27929e3b6d4175e9c1940aa016f8e3986f45cf6
Author: Heikki Linnakangas <[email protected]>

Modified Files
--------------
src/backend/utils/mmgr/generation.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)

Reply via email to