In kvm_vfio_pviommu_attach of vfio.c, there is a possible double free due to a logic error in the code.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: 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.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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
Workaround: 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.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- Google Android
Version range not reported
Evidence 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58847
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: android.googlesource.com
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: android.googlesource.com
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: android.googlesource.com
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: cve.now feed data
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: android.googlesource.com