[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100418-CVE-2022-50492-19b5@gregkh>
Date: Sat, 4 Oct 2025 17:51:17 +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-50492: drm/msm: fix use-after-free on probe deferral
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/msm: fix use-after-free on probe deferral
The bridge counter was never reset when tearing down the DRM device so
that stale pointers to deallocated structures would be accessed on the
next tear down (e.g. after a second late bind deferral).
Given enough bridges and a few probe deferrals this could currently also
lead to data beyond the bridge array being corrupted.
Patchwork: https://patchwork.freedesktop.org/patch/502665/
The Linux kernel CVE team has assigned CVE-2022-50492 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.12 with commit a3376e3ec81c5dd0622cbc187db76d2824d31c1c and fixed in 6.0.7 with commit 0a30a47741b6df1f9555a0fac6aebb7e8c363bad
Issue introduced in 3.12 with commit a3376e3ec81c5dd0622cbc187db76d2824d31c1c and fixed in 6.1 with commit 6808abdb33bf90330e70a687d29f038507e06ebb
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-50492
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/gpu/drm/msm/msm_drv.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/0a30a47741b6df1f9555a0fac6aebb7e8c363bad
https://git.kernel.org/stable/c/6808abdb33bf90330e70a687d29f038507e06ebb
Powered by blists - more mailing lists