[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022611-CVE-2022-49163-f5bc@gregkh>
Date: Wed, 26 Feb 2025 02:56:08 +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-49163: media: imx-jpeg: fix a bug of accessing array out of bounds
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: imx-jpeg: fix a bug of accessing array out of bounds
When error occurs in parsing jpeg, the slot isn't acquired yet, it may
be the default value MXC_MAX_SLOTS.
If the driver access the slot using the incorrect slot number, it will
access array out of bounds.
The result is the driver will change num_domains, which follows
slot_data in struct mxc_jpeg_dev.
Then the driver won't detach the pm domain at rmmod, which will lead to
kernel panic when trying to insmod again.
The Linux kernel CVE team has assigned CVE-2022-49163 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.33 with commit 02f9f97d54ffc85b50ad77f5b1f3c8f69cd17747
Fixed in 5.16.19 with commit 20c8b90430c5d6c4a3936eaa7c35aac670581487
Fixed in 5.17.2 with commit e209e6db2e527db6a93b14c2deedf969caca78fc
Fixed in 5.18 with commit 97558d170a1236280407e8d29a7d095d2c2ed554
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-49163
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/media/platform/imx-jpeg/mxc-jpeg.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/02f9f97d54ffc85b50ad77f5b1f3c8f69cd17747
https://git.kernel.org/stable/c/20c8b90430c5d6c4a3936eaa7c35aac670581487
https://git.kernel.org/stable/c/e209e6db2e527db6a93b14c2deedf969caca78fc
https://git.kernel.org/stable/c/97558d170a1236280407e8d29a7d095d2c2ed554
Powered by blists - more mailing lists