CVE-2026-58990
Received Received - Intake

Integer Overflow in Android Bluetooth L2CAP

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: Android (associated with Google Inc. or Open Handset Alliance)

Description
In l2c_fcr_process_peer_cfg_req of l2c_fcr.cc, there is a possible memory safety issue due to an integer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-02
Last Modified
2026-11-02
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD
CVE-2026-58990

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
Google Android 17
Google Android 16-qpr2
Google Android 16
Google Android 15
Google Android 14

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a memory safety issue caused by an integer overflow in the l2c_fcr_process_peer_cfg_req function of l2c_fcr.cc. It may allow remote attackers to disclose information without needing extra permissions or user interaction.

Impact Analysis

An attacker could exploit this to remotely access sensitive data on affected systems. Since no additional privileges or user interaction are required, the risk is higher for unpatched devices.

Mitigation Strategies

Apply the latest security patches from Google for Android to address the integer overflow issue in l2c_fcr.cc. Monitor official Android security bulletins for updates.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-58990. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...