All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49354: ata: pata_octeon_cf: Fix refcount leak in octeon_cf_probe
Date: Wed, 26 Feb 2025 03:10:28 +0100	[thread overview]
Message-ID: <2025022643-CVE-2022-49354-9be3@gregkh> (raw)

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ata: pata_octeon_cf: Fix refcount leak in octeon_cf_probe

of_find_device_by_node() takes reference, we should use put_device()
to release it when not need anymore.
Add missing put_device() to avoid refcount leak.

The Linux kernel CVE team has assigned CVE-2022-49354 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 4.9.318 with commit 7bd85c5ba1687daf54e3b6907673c3604b1e75cf
	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 4.14.283 with commit a4d3e5f1d7d4f8b5e3834fec0f057a762c55806b
	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 4.19.247 with commit 8d8ad067b90f231b8fdb14acee673ca4012f6045
	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 5.4.198 with commit d5a1e7f33c88780b279835d63665d7e38ccb671f
	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 5.10.122 with commit 19cb3ece14547cb1ca2021798aaf49a3f82643d1
	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 5.15.47 with commit 888312dc297a8a103f6371ef668c7e04f57a7679
	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 5.17.15 with commit c9782e1b21bee4b783a64b2a91e7e71406c21a21
	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 5.18.4 with commit fb2cb409b504bb3a69e65a17f3120328c8e50219
	Issue introduced in 3.8 with commit 43f01da0f2794b464ade2ffe1f780c69d7ce7b75 and fixed in 5.19 with commit 10d6bdf532902be1d8aa5900b3c03c5671612aa2

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-49354
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/ata/pata_octeon_cf.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/7bd85c5ba1687daf54e3b6907673c3604b1e75cf
	https://git.kernel.org/stable/c/a4d3e5f1d7d4f8b5e3834fec0f057a762c55806b
	https://git.kernel.org/stable/c/8d8ad067b90f231b8fdb14acee673ca4012f6045
	https://git.kernel.org/stable/c/d5a1e7f33c88780b279835d63665d7e38ccb671f
	https://git.kernel.org/stable/c/19cb3ece14547cb1ca2021798aaf49a3f82643d1
	https://git.kernel.org/stable/c/888312dc297a8a103f6371ef668c7e04f57a7679
	https://git.kernel.org/stable/c/c9782e1b21bee4b783a64b2a91e7e71406c21a21
	https://git.kernel.org/stable/c/fb2cb409b504bb3a69e65a17f3120328c8e50219
	https://git.kernel.org/stable/c/10d6bdf532902be1d8aa5900b3c03c5671612aa2

                 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=2025022643-CVE-2022-49354-9be3@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.