LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50233: Bluetooth: eir: Fix using strlen with hdev->{dev_name,short_name}

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: eir: Fix using strlen with hdev->{dev_name,short_name} Both dev_name and short_name are not guaranteed to be NULL terminated so this instead use strnlen and then attempt to determine if the resulting string needs to be truncated or not.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50233 is a Linux kernel Bluetooth issue. The kernel used string handling on Bluetooth device names that may not be properly terminated. The public record does not provide CVSS, confirmed impact, or exploitation evidence. Organizations should focus on Linux systems with Bluetooth enabled and apply vendor kernel updates when available.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize Bluetooth-capable Linux endpoints, laptops, embedded systems, and appliances once vendor fixes are available.

Technical view

In Linux Bluetooth EIR handling, hdev->dev_name and hdev->short_name are not guaranteed to be NULL-terminated. The fix replaces strlen behavior with strnlen and truncation checks. This suggests a memory-safety boundary issue, but the CVE record does not define impact, attack prerequisites, or affected distribution packages.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel code with Bluetooth functionality present or enabled. The source bundle lists Linux kernel versions but does not provide clear distribution-specific affected ranges. Systems without Bluetooth support may have lower practical exposure, but vendor confirmation is needed.

Exploitation context

No active exploitation is indicated. The CVE is not marked KEV, and the provided sources do not cite public exploitation, exploit availability, or attacker workflow. Trigger conditions are not detailed in the public record.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability detail, or distribution matrix. The upstream change centers on bounded string length handling for non-terminated Bluetooth device name fields. Further analysis should inspect vendor backports and kernel configuration exposure.

Mitigation direction

  • Check Linux distribution or appliance vendor advisories for CVE-2022-50233.
  • Upgrade to a kernel package containing the upstream stable fix.
  • Prioritize patching Linux systems with Bluetooth hardware or services enabled.
  • Track kernel package deployment and reboot systems after kernel updates.

Validation and detection

  • Inventory Linux hosts and record kernel versions.
  • Identify systems with Bluetooth support present or enabled.
  • Compare installed kernel packages against vendor fixed versions.
  • Confirm the upstream fix or vendor backport is included.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

cve · low confidence lookup

CVE-2022-50233 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4c3dbb2c312c9fafbac30d98c523b8b1f3455d78unaffected
LinuxLinux4.14, 0, 6.0affected
Weakness

CWE details

No CWE listed

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