
The next stage of CyberMeowfil (CVE-2026-43499 and 43074),Possibly biased toward vivo devices?
This repository documents methods, tools, and case records for Android kernel sample analysis, following the CyberMeowfia research line. The two routes are CVE-2026-43499 and CVE-2026-43074. It is a proof-of-concept disclosure: how to judge root cause, bind exact identity, choose a route, grade evidence, and explain success or failure.
This repository documents methods, tools, and case records for Android kernel sample analysis, following the CyberMeowfia research line. The two routes are CVE-2026-43499 and CVE-2026-43074. It is a proof-of-concept disclosure: how to judge root cause, bind exact identity, choose a route, grade evidence, and explain success or failure.
Documentation, offline analysis tools, a case matrix, and per-KMI reference source.
Claims bind to an exact kernel_sha256 and an evidence label. Sharing a KMI is not an identity.
Device images, prebuilt payloads, and turnkey runners are not included.
Documentation, offline analysis tools, a case matrix, and per-KMI reference source.
Claims bind to an exact kernel_sha256 and an evidence label. Sharing a KMI is not an identity.
Device images, prebuilt payloads, and turnkey runners are not included.
For a more detailed directory description, see docs/public/README.md. For terminology, see GLOSSARY.md.
Claims need a checkable sample identity. A race hit, a clean boot, or a successful syscall return is not closure. Record root cause, primitive, address domain, sticky write, privilege close, and authoritative readback as separate facts. Failures and disproofs are first-class results.
Claims need a checkable sample identity. A race hit, a clean boot, or a successful syscall return is not closure. Record root cause, primitive, address domain, sticky write, privilege close, and authoritative readback as separate facts. Failures and disproofs are first-class results.
Apache License 2.0. See LICENSE and NOTICE. For citation format, see CITATION.cff.