# CVE-2026-58825: Linux kernel use-after-free in fork.c dmabuf handling

Source: https://junglewise.ai/threats/cve-2026-58825-in-multiple-functions-of-fork-c-there-is-a-possible-use-after  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-02. Updated: 2026-11-02  
License: CC BY 4.0 with a link back

CVE-2026-58825 · Severity: info · Published 2026-11-02

A logic error in the Linux kernel's process management code fails to properly clean up memory references when processes unshare file descriptors. An attacker can exploit this use-after-free flaw to escalate from a regular user to administrator (root) privileges on an Android device without needing special permissions or user interaction.

Technologies: [Google Android kernel](https://junglewise.ai/threats/technologies/google-android-kernel). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## 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

## References

- [https://android.googlesource.com/kernel/common/+/009c5006c969826d37a2c5fc2721a7bb20d72555](https://android.googlesource.com/kernel/common/+/009c5006c969826d37a2c5fc2721a7bb20d72555)
- [https://android.googlesource.com/kernel/common/+/efe16a3021b9f95eb1cb83e98d0d1db9bff94ce4](https://android.googlesource.com/kernel/common/+/efe16a3021b9f95eb1cb83e98d0d1db9bff94ce4)

## Related threats

- [Android kernel SMMU stale TLB entry escalation](https://junglewise.ai/threats/cve-2026-56930-in-smmu-find-ste-of-smmu-c-there-is-a-possible-way-to-retain)
- [Android Kernel out-of-bounds read in KVM trace buffer initialization](https://junglewise.ai/threats/cve-2026-59048-in-rb-cpu-init-of-trace-c-there-is-a-possible-out-of-bounds-read)
- [Android Kernel KVM race condition memory corruption](https://junglewise.ai/threats/cve-2026-59045-in-multiple-locations-there-is-a-possible-memory-corruption-due)
- [Android kernel out-of-bounds write in pKVM MMU race condition](https://junglewise.ai/threats/cve-2026-59042-in-pkvm-pages-to-ppages-of-mmu-c-there-is-a-possible-out-of)
- [Android kernel integer overflow in VMA padding](https://junglewise.ai/threats/cve-2026-58845-in-multiple-locations-there-is-a-possible-out-of-bounds-write-due)