From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E631721C162 for ; Wed, 26 Feb 2025 02:27:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536872; cv=none; b=TY5d1t30VFzLApqdch2BbB8rOezXIDj8zs31xtzhwYdgotPxPc0ylnMDepWm25PR/ssSZyTMNlVSKZ5u9mHPSvxFMlVaMklBsClF11Zozs1zfKXiq1awvUMJGZHqQod4RkDwaC3/XdQjo12OWe64QJHxFbYJSp9xHLtdVa5dt3E= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536872; c=relaxed/simple; bh=poSQm4hHBTp1DldiPN81zWObThu7SLwBBVSQfVsjEa8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=KVlEUxsVZdSp1BapkVNtlu+RLWyhx2q9KxRzPkQgxCmMhNDcStzqget0lKYC3v+cUJK8ZmZsMRR1FxoxH83ikJq/3/ZLjfLszSqjpHSxg5CTdHmZUuvr/Elln/A/4CobOzdys6aLlfEzNkvXjEfmTtrvvkin4ADGk111etspK+Y= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=os7OsVFg; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="os7OsVFg" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B9AB8C4CEDD; Wed, 26 Feb 2025 02:27:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740536871; bh=poSQm4hHBTp1DldiPN81zWObThu7SLwBBVSQfVsjEa8=; h=From:To:Cc:Subject:Date:Reply-to:From; b=os7OsVFgBeIlPegiE6K9ahgL3vNCS8EKY+9TK6iV2AOoqil49GPjVbCk8jB5E3b8d gtgI7H88e2F4axnbICwcxnxHOQ4YKU0supOzQ6+Se5XEN3hDPKm4z5RK4CWOf8WcmJ nBX/QNF9iwOMYAyPXc/y1+SBsg6E2u7xFF1BYW34= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49680: ARM: exynos: Fix refcount leak in exynos_map_pmu Date: Wed, 26 Feb 2025 03:24:03 +0100 Message-ID: <2025022625-CVE-2022-49680-9dea@gregkh> X-Mailer: git-send-email 2.48.1 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3356; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=poSQm4hHBTp1DldiPN81zWObThu7SLwBBVSQfVsjEa8=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7qh5ufae7ofWnAXNrdqD00+owXasr+S/tjF0uv66RS BDa/L2wI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACZytY5hwYm8jXM191uXX5jw tuPp8rXHAveuzmCY757+6e/ZH5bnOF+UsP//6ZnDuTF0NwA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: ARM: exynos: Fix refcount leak in exynos_map_pmu of_find_matching_node() 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. of_node_put() checks null pointer. The Linux kernel CVE team has assigned CVE-2022-49680 to this issue. Affected and fixed versions =========================== Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 4.9.321 with commit 545ae5cbae839ce39bfe09828e413f1c916082de Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 4.14.286 with commit 31d09571bb071c20f6bdc0bb7ac1ef8dd2987c04 Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 4.19.250 with commit 7571bcecf01b69f0d3ec60ca41ce5d4c75411a4a Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.4.202 with commit f9b77a52937582a5b99a5a07e4ef1e2f48f87347 Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.10.127 with commit 68f28d52e6cbab8dcfa249cac4356d1d0573e868 Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.15.51 with commit d23f76018e17618559da9eea179d137362023f95 Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.18.8 with commit fc354856e9fad9cd36e2ad28f9da70716025055a Issue introduced in 3.17 with commit fce9e5bb25264153f9f002eada41757118d25ba9 and fixed in 5.19 with commit c4c79525042a4a7df96b73477feaf232fe44ae81 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-49680 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-exynos/exynos.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/545ae5cbae839ce39bfe09828e413f1c916082de https://git.kernel.org/stable/c/31d09571bb071c20f6bdc0bb7ac1ef8dd2987c04 https://git.kernel.org/stable/c/7571bcecf01b69f0d3ec60ca41ce5d4c75411a4a https://git.kernel.org/stable/c/f9b77a52937582a5b99a5a07e4ef1e2f48f87347 https://git.kernel.org/stable/c/68f28d52e6cbab8dcfa249cac4356d1d0573e868 https://git.kernel.org/stable/c/d23f76018e17618559da9eea179d137362023f95 https://git.kernel.org/stable/c/fc354856e9fad9cd36e2ad28f9da70716025055a https://git.kernel.org/stable/c/c4c79525042a4a7df96b73477feaf232fe44ae81