doing a quick analysis on 5D3.113, it is the
TUNE property table, starting at 0xF8B20000
you can dump it like that:
PropertyEditor.exe 0xF8000000-0xF8FFFFFF.BIN 0xB20000 0x2E0000
and it will spit out a property dump like this:

where you can see that this memory location is for properties 0x0101004D-0x0101007C with 5936 uint32 values.
before them there are properties 0x0101007E-0x0101008F with 376 uint32 values also looking like a offset table.
getting their value is as simple as reading a property. no need for memory locations.
modifying them, well, i would stick to patching it in-memory

good find!
would really be interesting if this is the FPN compensation table we could simply pass to MLV files.
(well not simply, a dark frame must be calculated from these values)