4 ms·
I tried it on my iPhone X and it triggers a kernel panic (agxk_mmu.cpp) when trying to allocate memory for WebKit. It seems it exhausts the memory so fast that
by KenanSulayman 8y ago
I tried it on my iPhone X and it triggers a kernel panic (agxk_mmu.cpp) when trying to allocate memory for WebKit.
It seems it exhausts the memory so fast that it triggers an assertion error somewhere?
Screenshot: https://i.imgur.com/6tDr44q.png https://i.imgur.com/6tDr44q.png
Full serial console log of the device: https://gist.githubusercontent.com/KenanSulayman/867cc399e9762189b3a52b2cf91781ca/raw/ded0b82a24464e969d2f84cd8edd25ac000f2a87/kern.log https://gist.githubusercontent.com/KenanSulayman/867cc399e97...
- jhabdas 8y agoHave you tried the backdoor yet? https://www.gnu.org/proprietary/malware-apple.html#back-doors https://www.gnu.org/proprietary/malware-apple.html#back-door...
- barbegal 8y agoThe log suggests the device is doing everything correctly. The exploit webpage requires huge amounts of memory to render correctly. It is consuming all the available memory causing allocations for backboardd to fail. The kernel then starts killing off idle processes to free up memory. I don't see a kernel panic there.
- amaccuish 8y agoDoes iOS not enforce reasonable memory limits on apps to prevent a panic?
- MBCook 8y agoIt does. Your app will get killed. The OS will be fine. My understanding is this bug uses up GPU memory/contexts, not normal system RAM, and that’s why it becomes an issue.
- amaccuish 8y agoAhh thank you :)
- swingline-747 8y agoOhh.. sneaky: a GPU DoS.
- MBCook 8y agoYeah. Of course it shouldn’t be possible, but I guess no one had thought of it before or they thought the risk was too low because they figured you’d have to make an app to do it not some random HTML on a webpage.