Re:First public macOS kernel memory corruption exploit on Ap...
by vsgherzi on Friday May 15, 2026 @12:38AM
(#48144620)
Hm that leaves more questions for me. Why does this path not have bounds checking, is think perhaps a limit of the clang flag or is it more simply a mistake of omission on apples part. Either way it seems like a bad look. I wish we’d get a post mortem
[ Parent
| on HN ]
There are no comments on this comment yet.