LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50044: net: qrtr: start MHI channel after endpoit creation

In the Linux kernel, the following vulnerability has been resolved: net: qrtr: start MHI channel after endpoit creation MHI channel may generates event/interrupt right after enabling. It may leads to 2 race conditions issues. 1) Such event may be dropped by qcom_mhi_qrtr_dl_callback() at check: if (!qdev || mhi_res->transaction_status) return; Because dev_set_drvdata(&mhi_dev->dev, qdev) may be not performed at this moment. In this situation qrtr-ns will be unable to enumerate services in device. --------------------------------------------------------------- 2) Such event may come at the moment after dev_set_drvdata() and before qrtr_endpoint_register(). In this case kernel will panic with accessing wrong pointer at qcom_mhi_qrtr_dl_callback(): rc = qrtr_endpoint_post(&qdev->ep, mhi_res->buf_addr, mhi_res->bytes_xferd); Because endpoint is not created yet. -------------------------------------------------------------- So move mhi_prepare_for_transfer_autoqueue after endpoint creation to fix it.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a race condition in Qualcomm QRTR over MHI handling. If an event arrives before endpoint setup is complete, the system may fail to enumerate services or panic. The sources do not provide CVSS, active exploitation evidence, or broad impact details.

Executive priority

Treat this as a targeted kernel stability risk, not a confirmed internet-scale emergency. Prioritize patch validation for Linux systems using Qualcomm MHI/QRTR functionality, while tracking vendor advisories for severity and affected package confirmation.

Technical view

The MHI transfer channel can generate callbacks immediately after being enabled. In qcom_mhi_qrtr_dl_callback(), that can race with driver data setup and qrtr_endpoint_register(), causing dropped events or qrtr_endpoint_post() use before endpoint creation. The fix starts MHI transfer after endpoint creation.

Likely exposure

Exposure appears limited to Linux kernels containing the affected QRTR/MHI driver path, especially systems using Qualcomm MHI-connected devices. The supplied affected version data is sparse and should be validated against distro kernel packages and the referenced stable commits.

Exploitation context

The bundle does not cite active exploitation, KEV listing, exploit maturity, remote reachability, or privilege requirements. The described outcome is reliability-impacting, including service enumeration failure and possible kernel panic when the race is hit.

Researcher notes

The source clearly explains the race and fix ordering, but does not provide CVSS, CWE, attack vector, privileges, or proof of exploitability. Affected version information is incomplete and should be mapped to downstream kernel builds before exposure claims.

Mitigation direction

  • Check vendor or distribution advisories for kernel packages containing the referenced stable fixes.
  • Update affected Linux kernels to a vendor-supported build that includes the QRTR/MHI fix.
  • Prioritize systems using Qualcomm MHI or QRTR-related hardware and drivers.
  • Avoid unsupported driver changes; disable unused affected components only under vendor guidance.

Validation and detection

  • Inventory Linux kernel versions and vendor package patch levels across relevant systems.
  • Confirm whether the referenced stable commits are present in deployed kernel source or changelogs.
  • Check whether QRTR and MHI support are enabled and used on the system.
  • Review kernel logs for QRTR service enumeration failures or unexplained kernel panics.
Prepared
Confidence
medium
Sources
5

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-50044 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
4Source 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
LinuxLinuxa2e2cc0dbb1121dfa875da1c04f3dff966fec162, a2e2cc0dbb1121dfa875da1c04f3dff966fec162, a2e2cc0dbb1121dfa875da1c04f3dff966fec162unaffected
LinuxLinux5.11, 0, 5.15.63, 5.19.4, 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.