Right now, there is no way to spot out-of-bounds reads or writes easily (unless the kernel has been compiled with KASAN or similar).
A custom allocator similar to libdislocator.so would help a lot.
One idea might be to, at the entry of kmalloc, patch in a jump to a similar emulated library and list the function (plus parameter mappings?) in the config.
Another idea might be to leave mapping of unallocated mem completely to the python layer.
Right now, there is no way to spot out-of-bounds reads or writes easily (unless the kernel has been compiled with KASAN or similar).
A custom allocator similar to
libdislocator.sowould help a lot.One idea might be to, at the entry of kmalloc, patch in a jump to a similar emulated library and list the function (plus parameter mappings?) in the config.
Another idea might be to leave mapping of unallocated mem completely to the python layer.