LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49202: Bluetooth: hci_uart: add missing NULL check in h5_enqueue

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: add missing NULL check in h5_enqueue Syzbot hit general protection fault in __pm_runtime_resume(). The problem was in missing NULL check. hu->serdev can be NULL and we should not blindly pass &serdev->dev somewhere, since it will cause GPF.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Bluetooth driver bug that can crash kernel execution when a missing NULL check reaches power-management code. The available sources do not show data theft, privilege escalation, or active exploitation. Business urgency is mainly stability and availability for systems using Bluetooth HCI UART/H5 support.

Executive priority

Schedule remediation through normal kernel patch cycles, faster for Bluetooth-dependent devices or environments where kernel crashes affect service availability. There is no cited evidence of active exploitation or confirmed high-impact compromise in the supplied sources.

Technical view

The flaw is in Linux Bluetooth hci_uart h5_enqueue. hu->serdev may be NULL, but the code could pass the derived device pointer into __pm_runtime_resume(), causing a general protection fault. The fix adds the missing NULL check. Severity, CVSS, and CWE are not provided in the bundle.

Likely exposure

Likely exposed assets are Linux systems that use or load the Bluetooth HCI UART H5 driver path. Exposure is less likely on systems without Bluetooth support, without this driver enabled, or on kernels carrying the referenced stable fixes. Exact distribution impact needs vendor kernel mapping.

Exploitation context

The source notes syzbot triggered a general protection fault. The bundle does not report public exploitation, KEV listing, exploit code, or attacker prerequisites. Treat this as a kernel availability risk unless vendor advisories provide stronger impact details.

Researcher notes

Evidence is limited to the CVE description and upstream stable commit references. The bundle lists no CVSS, CWE, CPEs, or exploit status. Validate impact by reviewing the exact kernel configuration, hci_uart usage, and whether downstream kernels backported the NULL-check fix.

Mitigation direction

  • Check Linux distribution advisories for CVE-2022-49202 coverage.
  • Update to a vendor kernel containing the referenced stable fix.
  • Disable unused Bluetooth support where operationally acceptable.
  • Prioritize embedded or edge systems that rely on Bluetooth UART paths.
  • Track vendor backports rather than relying only on upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions and vendor patch levels.
  • Identify systems with Bluetooth HCI UART or H5 support enabled.
  • Confirm whether kernel packages include the referenced stable commits.
  • Review crash telemetry for Bluetooth hci_uart general protection faults.
  • Check vendor advisories for distribution-specific affected versions.
Prepared
Confidence
medium
Sources
6

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-49202 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
5Source 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
LinuxLinuxd9dd833cf6d29695682ec7e7924c0d0992b906bc, d9dd833cf6d29695682ec7e7924c0d0992b906bc, d9dd833cf6d29695682ec7e7924c0d0992b906bc, d9dd833cf6d29695682ec7e7924c0d0992b906bcunaffected
LinuxLinux5.15, 0, 5.15.33, 5.16.19, 5.17.2, 5.18affected
Weakness

CWE details

No CWE listed

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