New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users
Status: Fixed
Owner:
Email to this user bounced
Closed: Jun 2015
Cc:



Sign in to add a comment
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.

 
bug320.cpp
2.8 KB Download
special_pool_crash.txt
6.7 KB View Download
Comment 1 by cevans@google.com, Apr 8 2015
Labels: Id-21873
Comment 2 by cevans@google.com, Jun 4 2015
Labels: CVE-2015-1726
Project Member Comment 4 by hawkes@google.com, Sep 21 2015
Labels: -Restrict-View-Commit
Sign in to add a comment