CVE-2026-45835VulnerabilityPublished 2 May 2026Updated 9 Jun 2026

l2cap_sock_new_connection_cb() · Bluetooth: L2CAP: Fix null-ptr-deref

Affects MicrosoftSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 06:59 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

microsoft-security-response-ce

What to do

Affected software

Product	Affected	Fixed in
Microsoft Security Response Center Microsoft	Affected =3.0 Microsoft Azure Linux 3.0 Azure Linux 3.0 kernel	Fixed in–

Description

CVE-2026-45835 is a vulnerability in Microsoft Bluetooth L2CAP component where a null pointer dereference occurs in the function l2cap_sock_new_connection_cb(). This flaw could cause a denial of service or system instability if triggered. The affected version is Microsoft product version 3.0. No CVSS score is provided, and there is no indication of known exploits in the wild. No patch or remediation details are currently available.

Impact

The primary impact is potential denial of service or system instability due to a null pointer dereference in the Bluetooth L2CAP connection handling. There is no evidence of exploitation in the wild or additional impacts such as privilege escalation or data disclosure.

Summary

This vulnerability involves a null pointer dereference in the Bluetooth L2CAP implementation within Microsoft software, specifically in the function l2cap_sock_new_connection_cb(). The flaw may lead to application or system crashes when handling new L2CAP socket connections. The affected version is explicitly stated as version 3.0 of the Microsoft product. No further technical details, exploit code, or mitigation instructions are provided in the available data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Oct 2026, 20:59 UTC

Technical details

References

Community reviews

Related threats