From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49342: net: ethernet: bgmac: Fix refcount leak in bcma_mdio_mii_register
Date: Wed, 26 Feb 2025 03:10:16 +0100 [thread overview]
Message-ID: <2025022641-CVE-2022-49342-1ad0@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: ethernet: bgmac: Fix refcount leak in bcma_mdio_mii_register
of_get_child_by_name() 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-49342 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.8 with commit 55954f3bfdacc5908515b0c306cea23e77fab740 and fixed in 5.17.15 with commit b51996e35bbfcc7a27d94dfeed5cc2429b2c0df4
Issue introduced in 4.8 with commit 55954f3bfdacc5908515b0c306cea23e77fab740 and fixed in 5.18.4 with commit 7fb1fe7d9a167205413f1de8db9f7d0f82c78286
Issue introduced in 4.8 with commit 55954f3bfdacc5908515b0c306cea23e77fab740 and fixed in 5.19 with commit b8d91399775c55162073bb2aca061ec42e3d4bc1
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-49342
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/net/ethernet/broadcom/bgmac-bcma-mdio.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/b51996e35bbfcc7a27d94dfeed5cc2429b2c0df4
https://git.kernel.org/stable/c/7fb1fe7d9a167205413f1de8db9f7d0f82c78286
https://git.kernel.org/stable/c/b8d91399775c55162073bb2aca061ec42e3d4bc1
reply other threads:[~2025-02-26 2:13 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=2025022641-CVE-2022-49342-1ad0@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.