# CVE-2026-56958: Google Pixel kernel out-of-bounds read in gf_algo.c

Source: https://junglewise.ai/threats/cve-2026-56958-google-pixel-kernel-out-of-bounds-read-in-gf-algo-c  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-15. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-56958 · Severity: medium · CVSS 5.5 · Published 2026-09-15

A kernel vulnerability in Google Pixel devices allows unauthorized access to sensitive system memory without requiring special privileges or user interaction. An attacker with local access could read confidential information stored in kernel memory, potentially including cryptographic keys, authentication tokens, or other sensitive data that could be used for further attacks.

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

## Quick answers

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

**How severe is CVE-2026-56958?** Medium severity, with a CVSS score of 5.5, published 15 September 2026.

**Which products and versions are affected?** Google Pixel Firmware prior to 2026-09-05 patch level.

**Is there a fix for CVE-2026-56958?** A patch was published on 2026-09-05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-56958 attacked?** It is attacked with local access, in device firmware.

**Am I affected by CVE-2026-56958?** Check whether you run Google Android or Google Pixel Firmware 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

The vulnerability is an out-of-bounds read in the gf_algo_get_cached_dump_data function in gf_algo.c, caused by a missing bounds check on memory access. The flaw is triggered locally and requires no additional execution privileges. An attacker with local code execution can read arbitrary kernel memory beyond intended buffer boundaries, leading to information disclosure. The vulnerability is addressed in Android Pixel devices receiving the 2026-09-05 security patch level or later.

## Affected products

- Google Pixel firmware prior to 2026-09-05 patch level

## Timeline

- 2026-09-15: disclosed
- 2026-09-05: patched

## References

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

## Related threats

- [Google Android Bluetooth buffer overflow in acquireMemory](https://junglewise.ai/threats/cve-2026-95405-in-acquirememory-of-bt-bqr-offload-cc-there-is-a-possible-way-to)
- [ST NFC HAL out-of-bounds write in global memory](https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-cc-there-is-a-possible-way-to)
- [Android HEVC decoder buffer overflow in sub_layer_hrd_parameters](https://junglewise.ai/threats/cve-2026-95397-in-sub-layer-hrd-parameters-of-hevc-decoder-there-is-a-possible)
- [Android framework memory exhaustion in message queue handling](https://junglewise.ai/threats/cve-2026-59632-in-respondreceivedmessage-of-mtsmessagecontroller-cpp-there-is-a)
- [Android use-after-free in UssiController connection listener](https://junglewise.ai/threats/cve-2026-59626-in-sendinfo-of-ussicontroller-cpp-there-is-a-possible-way-to)