On 24 July 2026 16:29:50 BST, Alperen Erkan <[email protected]> wrote: >ipc: Harden ipc_mqueue_send against null pointers, OOM, and race conditions > >I have written a patch for the `ipc_mqueue_send` implementation in GNU >Mach >(ipc/ipc_mqueue.c) that makes it safer against potential null pointer >accesses, allocation limit exhaustion under heavy message loads, and race >conditions on multi-core systems. You can already see the fixes for the >vulnerabilities that caught my attention whilst reading the code in the >patch. > >Thanks, >Alperen > >On Fri, Jul 24, 2026 at 4:39 PM Alperen Erkan <[email protected]> >wrote: > >> >> Thank you for the guidance and review! >> >> I have attached the clean patch file (0001-ipc_kmsg-fixes.patch) >directly >> to this email to prevent any whitespace or formatting issues. It >contains >> only the IPC memory fix and bounds checks. >> >> Regarding the documentation and communication: Understood. I will >> translate my technical notes into English and discuss all future >findings >> directly here on [email protected] >> >> Forwarding the patch to the bug-hurd mailing list for review and public >> discussion. >> >> Best regards, >> Alperen Erkan >> >
so you've written 3 patches in the space of 4 or so hours Thanks!
