# CVE-2026-0198: Android GDMC permission bypass in gem_msg.c

Source: https://junglewise.ai/threats/cve-2026-0198-in-is-pd-allowed-of-gem-msg-c-there-is-a-possible-permission  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-06. Updated: 2026-10-06  
License: CC BY 4.0 with a link back

CVE-2026-0198 · Severity: medium · CVSS 4.4 · Published 2026-10-06

A permission check vulnerability in Android's GDMC component allows an attacker with system-level privileges to bypass security controls and access sensitive information. This could expose user data or system information that should be protected from unauthorized access, requiring system-level execution privileges to exploit.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

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

**How severe is CVE-2026-0198?** Medium severity, with a CVSS score of 4.4, published 6 October 2026.

**Which products and versions are affected?** Google Android Prior to 2026-10-05 security patch level.

**Is there a fix for CVE-2026-0198?** Yes: fixed in Android security patch level 2026-10-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-0198 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-0198?** Check whether you run Google Android 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.

## How to fix

- Fixed in Android security patch level 2026-10-05 or later

## Technical details

A missing permission check in the is_pd_allowed function of gem_msg.c allows privilege bypass within the GDMC component on Android devices. The vulnerability requires System execution privileges and can lead to local information disclosure. No user interaction is required once system privileges are obtained.

## Affected products

- Google Android Prior to 2026-10-05 security patch level

## Timeline

- 2026-10-06: disclosed: Published in Pixel Update Bulletin—October 2026
- 2026-10-05: patched

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-10-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-10-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)