[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022631-CVE-2022-49278-b48d@gregkh>
Date: Wed, 26 Feb 2025 02:58:03 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49278: remoteproc: Fix count check in rproc_coredump_write()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: Fix count check in rproc_coredump_write()
Check count for 0, to avoid a potential underflow. Make the check the
same as the one in rproc_recovery_write().
The Linux kernel CVE team has assigned CVE-2022-49278 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.9 with commit 3afdc59e4390487f04f2435b7e8a6289984e0a1e and fixed in 5.10.110 with commit b97b305656a7013690e7b6e310f0e827e0bbff90
Issue introduced in 5.9 with commit 3afdc59e4390487f04f2435b7e8a6289984e0a1e and fixed in 5.15.33 with commit 34afac3c75fa08d6fabbab4c93f0a90618afaaa6
Issue introduced in 5.9 with commit 3afdc59e4390487f04f2435b7e8a6289984e0a1e and fixed in 5.16.19 with commit a8c3e53517985d69040a1b36a269e85f99cf0cea
Issue introduced in 5.9 with commit 3afdc59e4390487f04f2435b7e8a6289984e0a1e and fixed in 5.17.2 with commit 11572dad9fbadbd9269a2550f7e236b5b8c2d80c
Issue introduced in 5.9 with commit 3afdc59e4390487f04f2435b7e8a6289984e0a1e and fixed in 5.18 with commit f89672cc3681952f2d06314981a6b45f8b0045d1
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-49278
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/remoteproc/remoteproc_debugfs.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/b97b305656a7013690e7b6e310f0e827e0bbff90
https://git.kernel.org/stable/c/34afac3c75fa08d6fabbab4c93f0a90618afaaa6
https://git.kernel.org/stable/c/a8c3e53517985d69040a1b36a269e85f99cf0cea
https://git.kernel.org/stable/c/11572dad9fbadbd9269a2550f7e236b5b8c2d80c
https://git.kernel.org/stable/c/f89672cc3681952f2d06314981a6b45f8b0045d1
Powered by blists - more mailing lists