Searched refs:leak (Results 1 – 6 of 6) sorted by relevance
15 to extract—or “leak”—useful information from the other context. When the leaked22 index is in-bounds, leading the CPU to speculatively load and leak out-of-bounds60 about what memory any particular gadget can leak. This forces attackers to62 reliably leak interesting MTE tags. While this is a significant divergence179 On an unmitigated kernel, such a code sequence could be used to leak the187 leak information from the data submap, the kernel’s type segregation ensures242 attacker is able to successfully leak the contents of a given type when286 able to successfully leak the contents of the same-sized target allocation using555 data flow terminates and it is assumed that the caller or callee will leak560 leak in an exploitable manner.[all …]
52 # Exclude leak detection code that reads all memory
29 information to determine what code was responsible for the leak.
655 uint64_t * leak = IONew(uint64_t, extraAlloc); in IOHibernateSystemSleep() local656 assert(leak); in IOHibernateSystemSleep()658 leak[idx] = idx; in IOHibernateSystemSleep()
255 objects, which an attacker a priori doesn’t know without some information leak.
600 options CONFIG_ZLEAKS # Live zone leak debugging # <zleaks>