CVE-2022-50044 Details
Description
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.
A race condition vulnerability has been identified in the Linux kernel's QRTR (Qualcomm Remote Procedure Call Transport) implementation over the MHI (Mobile High-speed Interface) channel. This vulnerability arises because the MHI channel can generate an event or interrupt immediately after being enabled, potentially leading to two race condition scenarios. In the first scenario, the event may be dropped by the QRTR callback function, preventing the QRTR namespace from enumerating services on the device. In the second scenario, the event could be received after the device data has been set but before the QRTR endpoint is registered, causing a kernel panic by accessing an invalid pointer since the endpoint has not yet been created.
The vulnerability has been addressed by modifying the QRTR MHI channel handling to ensure that the MHI channel preparation for transfer is queued after the endpoint creation, preventing the race condition.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/68a838b84effb7b57ba7d50b1863fc6ae35a54ce | kernel.org | Patch |
| https://git.kernel.org/stable/c/a1a75f78a2937567946b1b756f82462874b5ca20 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c682fb70a7dfc25b848a4ff3a385b0471b470606 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.11, < 5.15.63 >= 5.16, < 5.19.4 6.0 rc1 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 13, 2025 | Initial Analysis | [email protected] |
| Jun 18, 2025 | New CVE Received | kernel.org |