CVE-2022-50044

published 18 Jun 2025 · updated 11 May 2026

net: qrtr: start MHI channel after endpoit creation

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 68a838b84effb7b57ba7d50b1863fc6ae35a54ce, Kernel a1a75f78a2937567946b1b756f82462874b5ca20 and Kernel c682fb70a7dfc25b848a4ff3a385b0471b470606.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.11, >=a2e2cc0dbb1121dfa875da1c04f3dff966fec162 <68a838b84effb7b57ba7d50b1863fc6ae35a54ce, >=a2e2cc0dbb1121dfa875da1c04f3dff966fec162 <a1a75f78a2937567946b1b756f82462874b5ca20, >=a2e2cc0dbb1121dfa875da1c04f3dff966fec162 <c682fb70a7dfc25b848a4ff3a385b0471b47060668a838b84effb7b57ba7d50b1863fc6ae35a54ce, a1a75f78a2937567946b1b756f82462874b5ca20, c682fb70a7dfc25b848a4ff3a385b0471b470606

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-50044 severity on Zeptric[![CVE-2022-50044](https://zeptric.io/badge/cve/CVE-2022-50044.svg)](https://zeptric.io/cve/CVE-2022-50044)