Security readout for executives and security teams
Plain-English summary
A race condition in Linux Bluetooth management can expose partially initialized work to a concurrent removal path. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability impact. Systems without Bluetooth hardware or the affected kernel code may have lower practical exposure.
Executive priority
Prioritize affected multi-user endpoints, shared Linux systems, and devices permitting untrusted local access. Treat remediation as a high-priority kernel update, but validate distribution backports before declaring exposure because upstream version labels alone may not map cleanly to packaged kernels.
Technical view
CWE-362 affects HCI management initialization. Concurrent hci_sock_sendmsg() and hci_sock_bind() paths can set and test HCI_MGMT without hci_dev_lock(), allowing mgmt_index_removed() to cancel uninitialized delayed work. The published fix initializes delayed work before setting HCI_MGMT while holding mgmt_chan_list_lock.
Likely exposure
The supplied record identifies affected Linux 6.0-era versions, with version boundaries involving 6.0.3 and 6.1. Its flattened version data is ambiguous. Confirm exposure using distribution advisories and kernel backport records, especially where untrusted users have local access and Bluetooth support is enabled.
Exploitation context
The CVSS vector requires local access and low privileges, with no user interaction. The supplied sources do not establish remote exploitation, public weaponization, or observed attacks. This CVE is not listed as KEV in the bundle, so active exploitation should not be claimed.
Researcher notes
The patch changes initialization ordering under mgmt_chan_list_lock rather than introducing global hci_dev_lock() serialization. The description explicitly notes that missing global serialization might cause other races and leaves broader correction to future work. That statement is a research lead, not evidence of another confirmed vulnerability or bypass.
Mitigation direction
- Install a vendor-supported kernel containing the referenced fix or its documented backport.
- Check distribution security guidance for exact fixed package versions.
- Restrict untrusted local account access until affected systems are updated.
- Consider disabling unnecessary Bluetooth functionality after operational and vendor review.
Validation and detection
- Record each system's running kernel and distribution package version.
- Confirm the vendor changelog includes either referenced commit or an equivalent backport.
- Identify systems with Bluetooth support enabled and accessible to local users.
- Review kernel logs for reports involving cancellation of uninitialized Bluetooth management work.
- Regression-test required Bluetooth management functions after updating.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-362: 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 lookupCVE-2022-50339 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/e53c6180db8dd09de94e0a3bdf4fef6f5f9dd6e6CVE reference, Linux
- https://git.kernel.org/stable/c/f74ca25d6d6629ffd4fd80a1a73037253b57d06bCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.