Quick answers
- Is CVE-2026-58825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58825 being exploited in the wild.
- How severe is CVE-2026-58825?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Google Android kernel versions prior to the fix commits.
- Is there a fix for CVE-2026-58825?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-58825 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-58825?
- Check whether you run Google Android kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a use-after-free in fork.c's unshare() syscall path: when a process calls unshare(CLONE_FILES), the kernel fails to clear the task's dmabuf_info pointer in certain code paths, leading to dangling references and potential memory corruption. An unprivileged local attacker can trigger this flaw to achieve privilege escalation with no additional execution privileges required.
Affected products
- Google Android kernel versions prior to the fix commits
Timeline
- 2026-11-02: disclosed