[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025123024-CVE-2022-50878-2067@gregkh>
Date: Tue, 30 Dec 2025 13:23:27 +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-50878: gpu: lontium-lt9611: Fix NULL pointer dereference in lt9611_connector_init()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
gpu: lontium-lt9611: Fix NULL pointer dereference in lt9611_connector_init()
A NULL check for bridge->encoder shows that it may be NULL, but it
already been dereferenced on all paths leading to the check.
812 if (!bridge->encoder) {
Dereference the pointer bridge->encoder.
810 drm_connector_attach_encoder(<9611->connector, bridge->encoder);
The Linux kernel CVE team has assigned CVE-2022-50878 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.150 with commit 3959e8faf8bf6bea619e8856c736db64e6eced37
Fixed in 5.15.75 with commit a29f7427041a943484f916157c43c46d3bbf25d4
Fixed in 5.19.17 with commit b2e4323e0020213f44dca6ffc815d66aef39f6f6
Fixed in 6.0.3 with commit 912f84e15e94ab87f5a7156aa1870090373d8304
Fixed in 6.1 with commit ef8886f321c5dab8124b9153d25afa2a71d05323
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-50878
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/lontium-lt9611.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/3959e8faf8bf6bea619e8856c736db64e6eced37
https://git.kernel.org/stable/c/a29f7427041a943484f916157c43c46d3bbf25d4
https://git.kernel.org/stable/c/b2e4323e0020213f44dca6ffc815d66aef39f6f6
https://git.kernel.org/stable/c/912f84e15e94ab87f5a7156aa1870090373d8304
https://git.kernel.org/stable/c/ef8886f321c5dab8124b9153d25afa2a71d05323
Powered by blists - more mailing lists