LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50386: Bluetooth: L2CAP: Fix user-after-free

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix user-after-free This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following trace: Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct kref *kref) Bluetooth: chan 0000000023c4974d Bluetooth: parent 00000000ae861c08 ================================================================== BUG: KASAN: use-after-free in __mutex_waiter_is_first kernel/locking/mutex.c:191 [inline] BUG: KASAN: use-after-free in __mutex_lock_common kernel/locking/mutex.c:671 [inline] BUG: KASAN: use-after-free in __mutex_lock+0x278/0x400 kernel/locking/mutex.c:729 Read of size 8 at addr ffff888006a49b08 by task kworker/u3:2/389

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-50386 is a Linux kernel Bluetooth L2CAP use-after-free flaw. A successful attack could compromise confidentiality, integrity, and availability. The source rates it high severity with CVSS 8.0. Exposure depends on affected kernel versions and whether Bluetooth/L2CAP is reachable in the environment.

Executive priority

Treat as a high-priority kernel maintenance issue, especially for Bluetooth-capable endpoints and embedded systems. It is not presented as actively exploited in the supplied sources, but the impact rating justifies prompt inventory, patch planning, and temporary Bluetooth reduction where operationally acceptable.

Technical view

The resolved kernel issue adds l2cap_chan_hold_unless_zero() after __l2cap_get_chan_blah() to prevent a use-after-free seen by KASAN in mutex locking during L2CAP channel handling. It is classified as CWE-416 and tied to Linux stable commits across multiple kernel branches.

Likely exposure

Most relevant exposure is Linux systems running affected kernel branches with Bluetooth functionality enabled or reachable. The CVSS vector is adjacent-network, low-privilege, no user interaction, so practical exposure is narrower than internet-facing services but important for endpoints, embedded devices, and servers with Bluetooth enabled.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. They support a high-impact memory-safety issue in Bluetooth L2CAP with adjacent access and low privileges, but they do not provide public exploit evidence or attack prevalence.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. The affected-version data is broad and branch-specific, so map exposure through downstream distro advisories rather than raw upstream version strings alone. Do not infer exploitability beyond the CVSS vector and kernel fix description.

Mitigation direction

  • Inventory Linux kernel versions and Bluetooth-enabled assets.
  • Apply vendor kernel updates containing the referenced stable fixes.
  • If Bluetooth is unnecessary, disable it pending patch validation.
  • Prioritize mobile, workstation, IoT, and embedded Linux fleets.
  • Track distro advisories for backported fixes and package names.

Validation and detection

  • Confirm running kernel versions against vendor advisories.
  • Check whether Bluetooth services or adapters are enabled.
  • Verify patched builds include the relevant stable commit for their branch.
  • Run regression tests for Bluetooth-dependent business workflows.
  • Document exceptions where Bluetooth cannot be disabled or patched promptly.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-50386 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.15.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2022-50386Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3df91ea20e744344100b10ae69a17211fcf5b207, 3df91ea20e744344100b10ae69a17211fcf5b207, 3df91ea20e744344100b10ae69a17211fcf5b207, 3df91ea20e744344100b10ae69a17211fcf5b207, 3df91ea20e744344100b10ae69a17211fcf5b207, 3df91ea20e744344100b10ae69a17211fcf5b207, 3df91ea20e744344100b10ae69a17211fcf5b207, 3df91ea20e744344100b10ae69a17211fcf5b207, 3df91ea20e744344100b10ae69a17211fcf5b207unaffected
LinuxLinux3.4, 0, 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.