Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop-In Allocator #14

Open
domenukk opened this issue Sep 9, 2019 · 0 comments
Open

Drop-In Allocator #14

domenukk opened this issue Sep 9, 2019 · 0 comments

Comments

@domenukk
Copy link
Member

domenukk commented Sep 9, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant