|
|
Windows kernel: use-after-free in HmgAllocateObjectAttr | |||
| Reported by cevans@google.com, Apr 7 2015 | Back to list | |||
Credit is to "Nils Sommer of bytegeist, working with Google Project Zero". I managed to get a bluescreen out of this on first try with Win 7 32-bit, special pool enabled on win32k. --- The PoC bug checks reliably with Special Pool enabled on writing to freed memory. A reference to the freed memory is held at offset +0x10 of the THREADINFO object. This memory is referenced in HmgAllocateObjectAttr which is called in multiple locations. The freed memory is a struct inside a Brush Object which is freed in the call NtGdiDeleteObjectApp. --- This bug is subject to a 90 day disclosure deadline. If 90 days elapse without a broadly available patch, then the bug report will automatically become visible to the public.
Comment 1
by
cevans@google.com,
Apr 8 2015
,
Jun 4 2015
,
Jun 9 2015
,
Sep 21 2015
|
||||
| ► Sign in to add a comment | ||||