Quick answers
- Is CVE-2026-58829 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58829 being exploited in the wild.
- How severe is CVE-2026-58829?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Google Android kernel.
- Is there a fix for CVE-2026-58829?
- 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-58829 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-58829?
- Check whether you run Google Android kernel. 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 fuse_backing_mmap() within backing.c, caused by manual manipulation of vma->vm_file and file reference counts that fails to properly handle reference counting during VMA setup. This allows local privilege escalation with no additional execution privileges required and no user interaction needed. The fix replaces manual reference handling with the vma_set_file() helper to ensure correct reference counting.
Affected products
- Google Android kernel
Timeline
- 2026-11-02: disclosed