[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061840-CVE-2022-50203-2286@gregkh>
Date: Wed, 18 Jun 2025 13:04:28 +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-50203: ARM: OMAP2+: display: Fix refcount leak bug
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ARM: OMAP2+: display: Fix refcount leak bug
In omapdss_init_fbdev(), of_find_node_by_name() will return a node
pointer with refcount incremented. We should use of_node_put() when
it is not used anymore.
The Linux kernel CVE team has assigned CVE-2022-50203 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.291 with commit bdbdf69d5b78c5712c60c0004fa6aed12da36e26
Fixed in 4.19.256 with commit 0b4f96b47ff8dc2fa35d03c4116927248796d9af
Fixed in 5.4.211 with commit 3e505298a75f0bbdc96e923e76e5d45d6c8f64a7
Fixed in 5.10.137 with commit 88d556029a78999b098d26a330bb6a7de166f426
Fixed in 5.15.61 with commit a89a865dc9f0600fd146224e314775b9efc9d845
Fixed in 5.18.18 with commit 496988a19d5c36fabf97c847db39167e42393c74
Fixed in 5.19.2 with commit 2629d171f3d6451724549d8d10d14ac6da37a7be
Fixed in 6.0 with commit 50b87a32a79bca6e275918a711fb8cc55e16d739
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-50203
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:
arch/arm/mach-omap2/display.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/bdbdf69d5b78c5712c60c0004fa6aed12da36e26
https://git.kernel.org/stable/c/0b4f96b47ff8dc2fa35d03c4116927248796d9af
https://git.kernel.org/stable/c/3e505298a75f0bbdc96e923e76e5d45d6c8f64a7
https://git.kernel.org/stable/c/88d556029a78999b098d26a330bb6a7de166f426
https://git.kernel.org/stable/c/a89a865dc9f0600fd146224e314775b9efc9d845
https://git.kernel.org/stable/c/496988a19d5c36fabf97c847db39167e42393c74
https://git.kernel.org/stable/c/2629d171f3d6451724549d8d10d14ac6da37a7be
https://git.kernel.org/stable/c/50b87a32a79bca6e275918a711fb8cc55e16d739
Powered by blists - more mailing lists