# CVE-2026-14447: Google Pixel firmware out-of-bounds address disclosure via off-by-one check

Source: https://junglewise.ai/threats/cve-2026-14447-in-ext-mem-obj-get-page-of-memss-mfw-c-there-is-a-possible-way-to  
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-14447 · Severity: info · Published 2026-11-10

A flaw in Google Pixel device firmware allows a local attacker with system-level privileges to obtain physical memory addresses outside valid bounds through an off-by-one error in the ext_mem_obj_get_page function. This could enable an attacker to read sensitive system information from memory and potentially escalate privileges or access restricted data.

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

## Quick answers

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

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

**Which products and versions are affected?** Google Pixel firmware.

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

**Am I affected by CVE-2026-14447?** Check whether you run Google Pixel Firmware. 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 off-by-one bounds check error in the ext_mem_obj_get_page function of memss-mfw.c allows return of out-of-bounds physical addresses. The vulnerability requires local system execution privileges and does not require user interaction. Exploitation leads to information disclosure of system memory.

## Affected products

- Google Pixel firmware

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

- [Google Pixel firmware heap buffer overflow in CLDMA audio processing](https://junglewise.ai/threats/cve-2026-59601-in-calculatesamplerate-of-cldma-alcedo-cc-there-is-a-possible)
- [Google Pixel firmware out-of-bounds write in NCI command handler](https://junglewise.ai/threats/cve-2026-59587-in-stpropnci-prop-st-build-set-custom-polling-cmd-of-stpropnci)
- [Google Pixel firmware out of bounds read/write in log formatting](https://junglewise.ai/threats/cve-2026-59574-in-notifypollingloopframes-of-hal-fwlog-cc-there-is-a-possible)
- [Google Pixel firmware information disclosure on warm reset](https://junglewise.ai/threats/cve-2026-58808-in-multiple-locations-there-is-a-possible-way-to-dump-secure)
- [Google Pixel firmware memory bounds check in secure boot](https://junglewise.ai/threats/cve-2026-58805-in-multiple-locations-there-is-a-possible-way-to-zero-arbitrary)