CVE-2026-58880

Published Oct 5, 2026 CVSS 3.1 · 7 High EPSS < 1% KEV · Not listed
Description
In handle_app_val_response of btif_rc.cc, there is a possible way to achieve code execution due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Analysis

AI-generated

Technical impact

In the Android Bluetooth stack, a race condition in the handle_app_val_response function can let an attacker run arbitrary code and gain higher privileges on the device. No user interaction is required, so the flaw can be triggered automatically by a malicious Bluetooth device or background process. This timing error in response handling permits a complete loss of device security.

Affected Systems

The vulnerability impacts Android devices that include the Bluetooth radio stack component referenced in btif_rc.cc. Specific Android version numbers are not disclosed, so all releases containing the vulnerable code path are at risk. Administrators should consult the official Google Security Bulletin for affected editions.

Risk and Exploitability

The CVSS score of 7.0 classifies this flaw as medium to high severity. The lack of an EPSS value leaves the exploitation likelihood uncertain, but the race condition allows local privilege escalation without additional privileges and can be triggered without user interaction. Although not listed in the CISA KEV catalog, its ability to fully compromise a device warrants urgent remediation. Attackers would need proximity or observed traffic to manipulate the race condition, lowering the barrier to exploitation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Android security patch released by the vendor.
  • Disable Bluetooth or restrict its use if an update is not yet available.
  • Remove any third‑party applications that have unnecessary Bluetooth permissions.
  • Set up monitoring to detect unusual Bluetooth traffic.

Generated by OpenCVE AI on October 5, 2026 at 22:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:o:google:android:16.0:qpr2_beta_1:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2_beta_2:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2_beta_3:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:2.3:o:google:android:16.0:-:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2_beta_1:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2_beta_2:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2_beta_3:*:*:*:*:*:*
cpe:2.3:o:google:android:17.0:-:*:*:*:*:*:*
Type Values Removed Values Added
Title Android Bluetooth Race Condition Enables Local Privilege Escalation
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Android Bluetooth Race Condition Enables Local Privilege Escalation
First Time appeared Google
Google android
Weaknesses CWE-362
Vendors & Products Google
Google android
Type Values Removed Values Added
Description In handle_app_val_response of btif_rc.cc, there is a possible way to achieve code execution due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
References
Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Sources

Status
PUBLISHED
Assigner
google_android
Published
Updated
Oct 6, 2026, 3:56 AM
Reserved
Jul 2, 2026, 6:06 AM
Status
Analyzed
Published
Oct 5, 2026, 7:17 PM
Modified
Nov 9, 2026, 6:20 PM