[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025123021-CVE-2022-50847-6766@gregkh>
Date: Tue, 30 Dec 2025 13:13:33 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50847: drm/bridge: it6505: Initialize AUX channel in it6505_i2c_probe
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/bridge: it6505: Initialize AUX channel in it6505_i2c_probe
During device boot, the HPD interrupt could be triggered before the DRM
subsystem registers it6505 as a DRM bridge. In such cases, the driver
tries to access AUX channel and causes NULL pointer dereference.
Initializing the AUX channel earlier to prevent such error.
The Linux kernel CVE team has assigned CVE-2022-50847 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit b5c84a9edcd418cd055becad6a22439e7c5e3bf8 and fixed in 6.0.16 with commit 8ed8505803774fc3f36a432718036c21cc51e2ba
Issue introduced in 5.18 with commit b5c84a9edcd418cd055becad6a22439e7c5e3bf8 and fixed in 6.1.2 with commit 172d4d64075075f955e6e416915e3f287eec514a
Issue introduced in 5.18 with commit b5c84a9edcd418cd055becad6a22439e7c5e3bf8 and fixed in 6.2 with commit e577d4b13064c337b83fe7edecb3f34e87144821
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-50847
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/bridge/ite-it6505.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/8ed8505803774fc3f36a432718036c21cc51e2ba
https://git.kernel.org/stable/c/172d4d64075075f955e6e416915e3f287eec514a
https://git.kernel.org/stable/c/e577d4b13064c337b83fe7edecb3f34e87144821
Powered by blists - more mailing lists