Is CVE-2026-58828 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-58828 being exploited in the wild.

How severe is CVE-2026-58828?

Informational severity, published 2 November 2026.

Which products and versions are affected?

Google Android kernel affected versions prior to fix commit 0285abdfbfb9f99898d647dafb2ea7d4bdd22527.

How is CVE-2026-58828 attacked?

It is attacked with local access, in an operating system.

Am I affected by CVE-2026-58828?

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.

CVE-2026-58828: Android kernel use-after-free in dmabuf accounting in base.c

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

A race condition in the Android kernel's dmabuf accounting code could allow a local attacker to trigger a use-after-free vulnerability. An attacker with regular user privileges could exploit this during concurrent exec() operations to achieve privilege escalation, gaining root access on an affected device.

Technologies: Google Android kernel. Vendors: Google.

Quick answers

Is CVE-2026-58828 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-58828 being exploited in the wild.
How severe is CVE-2026-58828?: Informational severity, published 2 November 2026.
Which products and versions are affected?: Google Android kernel affected versions prior to fix commit 0285abdfbfb9f99898d647dafb2ea7d4bdd22527.
Is there a fix for CVE-2026-58828?: Yes: fixed in Android kernel commit 0285abdfbfb9f99898d647dafb2ea7d4bdd22527 and later. Until then: Apply kernel patches that take a temporary reference on the task's dmabuf_info under task_lock() to prevent concurrent freeing during exec() or related operations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-58828 attacked?: It is attacked with local access, in an operating system.
Am I affected by CVE-2026-58828?: 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.

How to fix

Fixed in: Android kernel commit 0285abdfbfb9f99898d647dafb2ea7d4bdd22527 and later

Apply kernel patches that take a temporary reference on the task's dmabuf_info under task_lock() to prevent concurrent freeing during exec() or related operations.

Technical details

A use-after-free vulnerability exists in fs/proc/base.c in functions proc_dmabuf_rss_show, proc_dmabuf_rss_hwm_show, proc_dmabuf_rss_hwm_write, and proc_dmabuf_pss_show due to a race condition where a task's dmabuf_info struct can be freed by exec() while being read without holding a reference. An unprivileged local attacker can trigger this race by calling exec() concurrently with reading procfs dmabuf accounting files, leading to use-after-free and privilege escalation.

Affected products

Google Android kernel affected versions prior to fix commit 0285abdfbfb9f99898d647dafb2ea7d4bdd22527

Timeline

2026-11-02: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.