[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061823-CVE-2022-50155-6af6@gregkh>
Date: Wed, 18 Jun 2025 13:03:40 +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-50155: mtd: parsers: ofpart: Fix refcount leak in bcm4908_partitions_fw_offset
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mtd: parsers: ofpart: Fix refcount leak in bcm4908_partitions_fw_offset
of_find_node_by_path() 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-50155 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit bb17230c61a6424b622e92006ec52ba23aa5a967 and fixed in 5.15.61 with commit 762475464982b15014f364ec0cf2a843407f5af1
Issue introduced in 5.13 with commit bb17230c61a6424b622e92006ec52ba23aa5a967 and fixed in 5.18.18 with commit 3193c3a3f4fca65cb06d9d48d07fb96bc1f5b2bd
Issue introduced in 5.13 with commit bb17230c61a6424b622e92006ec52ba23aa5a967 and fixed in 5.19.2 with commit 01bc3840d943cf725dea6ca13e11ffda82bad49a
Issue introduced in 5.13 with commit bb17230c61a6424b622e92006ec52ba23aa5a967 and fixed in 6.0 with commit e607879b0da18c451de5e91daf239cc2f2f8ff2d
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-50155
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/mtd/parsers/ofpart_bcm4908.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/762475464982b15014f364ec0cf2a843407f5af1
https://git.kernel.org/stable/c/3193c3a3f4fca65cb06d9d48d07fb96bc1f5b2bd
https://git.kernel.org/stable/c/01bc3840d943cf725dea6ca13e11ffda82bad49a
https://git.kernel.org/stable/c/e607879b0da18c451de5e91daf239cc2f2f8ff2d
Powered by blists - more mailing lists