@hackyzh profile picture
Mmm @hackyzh

Chrome GPU sandbox escape and Anroid Kernel Stuff.

Joined February 2018
  • Tweets 607
  • Following 600
  • Followers 3,098
69 Photos and videos
Mmm@hackyzh
Jun 9
write fuzzer. It's a joke.😅
1
702
Mmm@hackyzh
Jun 4
It's extremely difficult. Let's see if this vulnerability can enable complete RCE without renderer RCE, relying on a single vulnerability.
2
7
105
7,251
Mmm@hackyzh
Jun 2
Android Security Bulletin—June 2026  |  Android Open Source Project
11
2,096
Mmm@hackyzh
May 29
chromereleases.googleblog.co…

Chrome Releases

Release updates from the Chrome team

chromereleases.googleblog.com
3
859
Mmm@hackyzh
May 12
I'd like to ask everyone, after the Chrome VRP automatic update policy was implemented, are the bounties still being paid normally for vulnerabilities submitted before the new rules were introduced?🤣
1
5
1,549
Mmm@hackyzh
May 9
Found 1 android 0-click memory corruption vuln.However, it seems that the upstream issue was resolved in March.🤡Fortunately, it was just a minor OOB read.#0click
4
1
73
6,704
Mmm@hackyzh
May 1
😅Chrome VRP is dead
Google VRP (Google Bug Hunters)
@GoogleVRP
Apr 30
📣📢 Calling all Android and Chrome bug hunters 🧑‍💻🔎! We're updating our Android & Chrome VRP programs to ensure we can continue to reward the most challenging and impactful vulnerabilities researchers find in our products. For details, 👇 bughunters.google.com/blog/e…
1
10
1,934
Mmm@hackyzh
Apr 25
chromium.googlesource.com/ch… Demonstrating controlled read or write Mojom interfaces to demonstrate controlled reads or controlled writes in privileged processes are available in vrp_flags.mojom.

2
6
42
5,927
Mmm@hackyzh
Apr 25
`The controlled read or controlled write poc must be included in your initial report - we will not consider submissions added at a later time.` That's ridiculous.
3
839
Mmm retweeted
Numen Cyber@numencyber
Apr 13
Exploring Android ROOT via CVE-2025–21479 medium.com/@numencyberlabs/e…

Exploring Android ROOT via CVE-2025–21479

Google’s June 2025 security bulletin patched CVE-2025–21479, a vulnerability that was already being exploited in the wild. A few weeks…

medium.com
36
142
12,753
Mmm retweeted
Numen Cyber@numencyber
Apr 6
CVE-2026–5283: Uninitialized GPU Memory Disclosure via Partial Clear in ANGLE (Chrome WebGL) medium.com/@numencyberlabs/c…

CVE-2026–5283: Uninitialized GPU Memory Disclosure via Partial Clear in ANGLE (Chrome WebGL)

Summary

medium.com
1
21
80
9,604
Mmm@hackyzh
Mar 1
Interesting bugs, from Chrome to kernel crash on some device without MTE.
0:45
3
70
7,857
Mmm@hackyzh
Feb 6
git.codelinaro.org/clo/la/pl… I saw this patch a few months ago, but I haven't been able to create a reproducible proof-of-concept (PoC).
1
16
2,525
Mmm retweeted
Eduardo Vela@sirdarckcat
Jan 14
We are hiring! CPU security stuff google.com/about/careers/app…

3
27
194
22,170
[446722008][reward: $100000] heap-use-after-free in content::indexed_db::Database::connections_ when force_closing_ is true crbug.com/446722008

2
43
290
174,285
Mmm@hackyzh
Jan 2
MSRC is really ridiculous. I don't know if they're refusing bounties or what. I accidentally discovered and submitted OOB Write and UAF vulnerabilities, and they either said the vulnerabilities were low-risk or that they couldn't reproduce them in the latest version.
8
4
60
19,194
Mmm@hackyzh
Jan 2
Comparatively, I prefer Google. In the past, when I submitted vulnerabilities to Google, at least they would keep in touch with me. After Microsoft shut down its services, they rarely responded anymore.
1
7
1,385
Mmm@hackyzh
Jan 2
So, it's best not to submit vulnerabilities to MSRC, since they don't seem to care much about vulnerabilities and are even less concerned about the security of their own products.🤡
1
17
1,399
Mmm@hackyzh
18 Dec 2025
Interesting
The Lunduke Journal
@LundukeJournal
17 Dec 2025
Rust programmers re-wrote a portion of the Linux kernel (Android's Binder) in Rust. (Because, it would seem, re-writing working code in Rust is a religious obligation for many.) That code was published with the Linux kernel update a few weeks back. Yesterday, it was revealed that there was a vulnerability in that code. That vulnerability (which could take down an entire system) is due to memory corruption in the "memory safe" Rust code. If you investigate the specific, offending Rust code, you'll find that the code is marked "unsafe". Which is a common word you will find throughout all Rust code within the Linux Kernel. lore.kernel.org/linux-cve-an…
2
1,446
Mmm@hackyzh
15 Dec 2025
突然看到有人搞了个人生k线，意外这么火，X上喜欢八字命理玄学的这么多吗。这行碰到骗子，邪师的概率不少的。碰到骗子还好，邪师的话就惨了。
949
Load more