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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025061843-CVE-2022-50044-0b6b@gregkh>
Date: Wed, 18 Jun 2025 13:01:49 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50044: net: qrtr: start MHI channel after endpoit creation

From: Greg Kroah-Hartman <gregkh@...nel.org>

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.

The Linux kernel CVE team has assigned CVE-2022-50044 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.11 with commit a2e2cc0dbb1121dfa875da1c04f3dff966fec162 and fixed in 5.15.63 with commit c682fb70a7dfc25b848a4ff3a385b0471b470606
	Issue introduced in 5.11 with commit a2e2cc0dbb1121dfa875da1c04f3dff966fec162 and fixed in 5.19.4 with commit a1a75f78a2937567946b1b756f82462874b5ca20
	Issue introduced in 5.11 with commit a2e2cc0dbb1121dfa875da1c04f3dff966fec162 and fixed in 6.0 with commit 68a838b84effb7b57ba7d50b1863fc6ae35a54ce

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-50044
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	net/qrtr/mhi.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/c682fb70a7dfc25b848a4ff3a385b0471b470606
	https://git.kernel.org/stable/c/a1a75f78a2937567946b1b756f82462874b5ca20
	https://git.kernel.org/stable/c/68a838b84effb7b57ba7d50b1863fc6ae35a54ce