[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050143-CVE-2022-49848-0e49@gregkh>
Date: Thu, 1 May 2025 16:10:38 +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-49848: phy: qcom-qmp-combo: fix NULL-deref on runtime resume
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
phy: qcom-qmp-combo: fix NULL-deref on runtime resume
Commit fc64623637da ("phy: qcom-qmp-combo,usb: add support for separate
PCS_USB region") started treating the PCS_USB registers as potentially
separate from the PCS registers but used the wrong base when no PCS_USB
offset has been provided.
Fix the PCS_USB base used at runtime resume to prevent dereferencing a
NULL pointer on platforms that do not provide a PCS_USB offset (e.g.
SC7180).
The Linux kernel CVE team has assigned CVE-2022-49848 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.0 with commit fc64623637da5e964566628bc0e660e93dc7a395 and fixed in 6.0.9 with commit c559a8b5cfa3db196ced0257b288f17027621348
Issue introduced in 6.0 with commit fc64623637da5e964566628bc0e660e93dc7a395 and fixed in 6.1 with commit 04948e757148f870a31f4887ea2239403f516c3c
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-49848
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/phy/qualcomm/phy-qcom-qmp-combo.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/c559a8b5cfa3db196ced0257b288f17027621348
https://git.kernel.org/stable/c/04948e757148f870a31f4887ea2239403f516c3c
Powered by blists - more mailing lists