# CVE-2026-58757: Samsung MFC heap buffer overflow in enc_roi_buffer allocation

Source: https://junglewise.ai/threats/cve-2026-58757-in-mfc-alloc-enc-roi-buffer-of-mfc-buf-c-there-is-a-possible-out  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-58757 · Severity: info · Published 2026-11-10

Samsung's MFC (Multi-Format Codec) driver, used for video encoding and decoding on mobile devices, contains a heap buffer overflow in the enc_roi_buffer allocation function. A local attacker can exploit this to achieve privilege escalation without requiring special permissions or user interaction, potentially gaining control of the device.

Technologies: [Google Pixel Devices](https://junglewise.ai/threats/technologies/pixel-devices). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-58757 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-58757 being exploited in the wild.

**How severe is CVE-2026-58757?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Google Pixel Devices Prior to 2026-11-05 security patch level.

**Is there a fix for CVE-2026-58757?** 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-58757 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-58757?** Check whether you run Google Pixel Devices 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

An out-of-bounds write vulnerability exists in mfc_alloc_enc_roi_buffer() in mfc_buf.c due to improper heap buffer size validation. This allows a local attacker to overflow the heap buffer and corrupt adjacent memory, leading to privilege escalation. No special privileges or user interaction are required for exploitation.

## Affected products

- Google Pixel devices Prior to 2026-11-05 security patch level

## Timeline

- 2026-11-10: disclosed

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01)

## Related threats

- [PowerVR GPU kernel use-after-free in fence identifier handling](https://junglewise.ai/threats/cve-2026-59609-in-fence-manager-extract-iif-of-fence-manager-c-there-is-a)
- [Google Pixel Face Auth TA privilege escalation in TzPipelineInputExtractor](https://junglewise.ai/threats/cve-2026-59607-in-tzpipelineinputextractor-of-tzpipelineinputextractor-cpp-there)
- [Pixel HWCodec Firmware heap buffer overflow in encoder](https://junglewise.ai/threats/cve-2026-59594-in-spm-alloc-of-encoder-there-is-a-possible-heap-buffer-overflow)
- [Pixel devices out-of-bounds write in graphics execution](https://junglewise.ai/threats/cve-2026-58804-in-executegraphcommand-of-multiple-files-there-is-a-possible-way)
- [ARM SMMU v3 stale stream table entry information disclosure](https://junglewise.ai/threats/cve-2026-58801-in-smmu-domain-config-s1-of-arm-smmu-v3-c-there-is-a-possible-way)