CVE-2026-58679

Google · Android

A heap buffer overflow in the Android kernel function gf_ta_test_set_config allows for local escalation of privilege without requiring user interaction.

Executive summary

A heap buffer overflow vulnerability in the Google Android kernel could allow a local attacker to achieve unauthorized escalation of privileges.

Vulnerability

The vulnerability is a heap buffer overflow located in the gf_ta_test_set_config function within the file gf_ta_test.c. An attacker with local access can trigger this flaw without requiring elevated privileges or user interaction to gain higher system permissions.

Business impact

Successful exploitation of this vulnerability enables a local attacker to escalate their privileges, potentially gaining full control over the compromised device. Given the high CVSS score of 8.4, this poses a significant risk to data confidentiality, integrity, and availability, particularly in enterprise environments where mobile devices may access sensitive corporate resources.

Remediation

Immediate Action: Apply the latest security patches provided by Google through the official Android security bulletin process as soon as they become available for your specific device model.

Proactive Monitoring: Monitor system logs for unusual kernel-level activity or unexpected crashes that may indicate an attempted heap memory corruption.

Compensating Controls: Ensure that security features such as hardware backed keystores and restricted application sandboxing remain enabled to limit the potential impact of an escalated session.

Exploitation status

Public Exploit Available: No confirmed public exploit available.

Analyst recommendation

This vulnerability represents a significant security risk for the Android ecosystem due to the potential for privilege escalation. Administrators should prioritize the deployment of vendor security updates to all managed Android devices to mitigate the risk of local exploitation.

More Google CVEs all →

History

CVE Brief tracked this CVE 1 day before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 8.4 (3.1)
  4. Analyst report written

Sources