Skip to content

Conversation

@langston-barrett
Copy link
Contributor

Towards #3541. I targeted the libafl_qemu fuzzers first since they use a huge C library, which might make them more prone to memory corruption. They didn't use mimalloc already, wasn't sure if this was just an oversight?

@domenukk
Copy link
Member

I'm not sure if the C part uses the rust allocator at all?

@langston-barrett
Copy link
Contributor Author

I'm not sure if the C part uses the rust allocator at all?

Right, but it could overwrite e.g., heap metadata of the Rust allocations right? In any case, the Rust code certainly uses the allocator and benefits from additional safety.

@domenukk
Copy link
Member

Mimalloc also has a feature that enables a bunch of security checks btw.

I don't think the extra security is needed but also cannot hurt :)

@langston-barrett
Copy link
Contributor Author

Yeah, I wouldn't think of it so much in terms of security as in terms of extra protection against coding errors that result in memory corruption.

@0xalpharush
Copy link

Should this set these options https://source.android.com/docs/security/test/scudo? LLVM's default seem to effectively disable the mitigations

@domenukk domenukk merged commit fff9464 into AFLplusplus:main Nov 28, 2025
109 of 114 checks passed
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

Successfully merging this pull request may close these issues.

3 participants