It would be very surprised if this isn't just an atop bug. Can it be exploited? Considering the error messages, the possibility is high. I don't like to see i

It would be very surprised if this isn't just an atop bug. Can it be exploited? Considering the error messages, the possibility is high. I don't like to see it as "Problem with the heap". As someone who played lots of CTF and is quite sufficient in exploiting such bugs, i would much rather see those things framed as "Problems with the glibc allocator". If we just wouldn't use inline metadata, or verify it's integrity (smth like scudo but not broken), all of the security issues with the heap would just be gone. If you get to work with frameworks/languages that are more flexible when it comes to allocate memory (thinking about zig and it's amazing allocator abstraction here) you quickly realize that malloc and free are an insanely simplistic api for what is one of the most difficult and important problems in programming: memory allocation. There is also no excuse for the error messages being that bad. Because the reality is that most systems programmers will have to debug those at some point.