From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49421: video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup
Date: Wed, 26 Feb 2025 03:11:35 +0100 [thread overview]
Message-ID: <2025022654-CVE-2022-49421-6067@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup
of_parse_phandle() returns a node pointer with refcount incremented, we should
use of_node_put() on it when not need anymore. Add missing of_node_put() to
avoid refcount leak.
The Linux kernel CVE team has assigned CVE-2022-49421 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 4.9.318 with commit 6c92711db7c90f78e0b67ac2a8944d0fe7e12d83
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 4.14.283 with commit 2e2e2c71b2642289438392edbf5d08cdbc0b138b
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 4.19.247 with commit 51eb1bb6baeb478538dd4ec6459fd68c44a855b1
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 5.4.198 with commit 8db59df7f5826e104db82cfddbf22a33a151193e
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 5.10.121 with commit c1c4405222b6fc98c16e8c2aa679c14e41d81465
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 5.15.46 with commit f2dfb4ab887d67be7d0892ba041d3c8d738d3356
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 5.17.14 with commit bbb2a24e863b6a10129546a0a4ceea2f07deec39
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 5.18.3 with commit 38d245cebf545338a6bc1c7762023de3fbecd7b7
Issue introduced in 3.17 with commit d10715be03bd8bad59ddc50236cb140c3bd73c7b and fixed in 5.19 with commit b23789a59fa6f00e98a319291819f91fbba0deb8
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-49421
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/video/fbdev/amba-clcd.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/6c92711db7c90f78e0b67ac2a8944d0fe7e12d83
https://git.kernel.org/stable/c/2e2e2c71b2642289438392edbf5d08cdbc0b138b
https://git.kernel.org/stable/c/51eb1bb6baeb478538dd4ec6459fd68c44a855b1
https://git.kernel.org/stable/c/8db59df7f5826e104db82cfddbf22a33a151193e
https://git.kernel.org/stable/c/c1c4405222b6fc98c16e8c2aa679c14e41d81465
https://git.kernel.org/stable/c/f2dfb4ab887d67be7d0892ba041d3c8d738d3356
https://git.kernel.org/stable/c/bbb2a24e863b6a10129546a0a4ceea2f07deec39
https://git.kernel.org/stable/c/38d245cebf545338a6bc1c7762023de3fbecd7b7
https://git.kernel.org/stable/c/b23789a59fa6f00e98a319291819f91fbba0deb8
reply other threads:[~2025-02-26 2:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022654-CVE-2022-49421-6067@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.