linux-cve-announce - CVE-2022-49650: dmaengine: qcom: bam

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: <2025022620-CVE-2022-49650-c3d8@gregkh>
Date: Wed, 26 Feb 2025 03:23:33 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49650: dmaengine: qcom: bam_dma: fix runtime PM underflow

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

dmaengine: qcom: bam_dma: fix runtime PM underflow

Commit dbad41e7bb5f ("dmaengine: qcom: bam_dma: check if the runtime pm enabled")
caused unbalanced pm_runtime_get/put() calls when the bam is
controlled remotely. This commit reverts it and just enables pm_runtime
in all cases, the clk_* functions already just nop when the clock is NULL.

Also clean up a bit by removing unnecessary bamclk null checks.

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


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

	Issue introduced in 4.17 with commit dbad41e7bb5f4b9949ff5ea1d76c20711f326308 and fixed in 5.15.54 with commit 2f6ded79068cac8cff41d5d5632564165d98ee12
	Issue introduced in 4.17 with commit dbad41e7bb5f4b9949ff5ea1d76c20711f326308 and fixed in 5.18.11 with commit b702a1077b51fcb39507cc3bd39206f539319a96
	Issue introduced in 4.17 with commit dbad41e7bb5f4b9949ff5ea1d76c20711f326308 and fixed in 5.19 with commit 0ac9c3dd0d6fe293cd5044cfad10bec27d171e4e

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-49650
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:
	drivers/dma/qcom/bam_dma.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/2f6ded79068cac8cff41d5d5632564165d98ee12
	https://git.kernel.org/stable/c/b702a1077b51fcb39507cc3bd39206f539319a96
	https://git.kernel.org/stable/c/0ac9c3dd0d6fe293cd5044cfad10bec27d171e4e