Linker script not placing MB_MEM2 in SRAM2

I'm using a NUCLEO-WB55RG board and if I create a new project in STM32CubeIDE 1.12.0 and enable the STM32_WPAN and HeartRate example it doesn't work because the different buffers that need to be in SRAM2 is not placed there.

The app_entry.c defines these buffers like this:

PLACE_IN_SECTION("MB_MEM2") ALIGN(4) static uint8_t EvtPool[POOL_SIZE];
PLACE_IN_SECTION("MB_MEM2") ALIGN(4) static TL_CmdPacket_t SystemCmdBuffer;
PLACE_IN_SECTION("MB_MEM2") ALIGN(4) static uint8_t SystemSpareEvtBuffer[sizeof(TL_PacketHeader_t) + TL_EVT_HDR_SIZE + 255U];
PLACE_IN_SECTION("MB_MEM2") ALIGN(4) static uint8_t BleSpareEvtBuffer[sizeof(TL_PacketHeader_t) + TL_EVT_HDR_SIZE + 255];

The automatically generated linker script contains the following, which ends up placing the buffers in RAM1 if I look at the address at runtime using the debugger.

/* Specify the memory areas */
MEMORY
{
FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 512K
RAM1 (xrw) : ORIGIN = 0x20000008, LENGTH = 0x2FFF8
RAM_SHARED (xrw) : ORIGIN = 0x20030000, LENGTH = 10K
}
 
<--snipped-->
 
 MB_MEM1 (NOLOAD) : { *(MB_MEM1) } >RAM_SHARED
 
 /* used by the startup to initialize .MB_MEM2 data */
 _siMB_MEM2 = LOADADDR(.MB_MEM2);
 .MB_MEM2 :
 {
 _sMB_MEM2 = . ;
 *(.MB_MEM2) ;
 _eMB_MEM2 = . ;
 } >RAM_SHARED AT> FLASH

If I instead create a new project based on the BLE_HeartRate example from "Example Selector", the linker script instead contain:

/* Specify the memory areas */
MEMORY
{
FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 512K
RAM1 (xrw) : ORIGIN = 0x20000008, LENGTH = 0x2FFF8
RAM_SHARED (xrw) : ORIGIN = 0x20030000, LENGTH = 10K
}
 
<--snipped-->
 
 MB_MEM1 (NOLOAD) : { *(MB_MEM1) } >RAM_SHARED
 MB_MEM2 (NOLOAD) : { _sMB_MEM2 = . ; *(MB_MEM2) ; _eMB_MEM2 = . ; } >RAM_SHARED

And this works just fine, and the buffers are placed in SRAM2.

I can solve the issue by creating my own section, placing it in RAM_SHARED, or by just editing app_entry.c to place them in MB_RAM1 which is also correctly placed in RAM_SHARED / SRAM2, but if feels like this is a bug that will probably confuse a lot of other people as well.

(My linked script knowledge is a bit limited, so I don't really understand why the auto-generated linker script ends up placing the section in the wrong place.)