linux-cve-announce - CVE-2022-49285: iio: accel: mma8452: use the correct logic to get mma8452

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025022632-CVE-2022-49285-627c@gregkh>
Date: Wed, 26 Feb 2025 02:58:10 +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-49285: iio: accel: mma8452: use the correct logic to get mma8452_data

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

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

iio: accel: mma8452: use the correct logic to get mma8452_data

The original logic to get mma8452_data is wrong, the *dev point to
the device belong to iio_dev. we can't use this dev to find the
correct i2c_client. The original logic happen to work because it
finally use dev->driver_data to get iio_dev. Here use the API
to_i2c_client() is wrong and make reader confuse. To correct the
logic, it should be like this

  struct mma8452_data *data = iio_priv(dev_get_drvdata(dev));

But after commit 8b7651f25962 ("iio: iio_device_alloc(): Remove
unnecessary self drvdata"), the upper logic also can't work.
When try to show the avialable scale in userspace, will meet kernel
dump, kernel handle NULL pointer dereference.

So use dev_to_iio_dev() to correct the logic.

Dual fixes tags as the second reflects when the bug was exposed, whilst
the first reflects when the original bug was introduced.

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

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

	Issue introduced in 4.4 with commit c3cdd6e48e35b7a02f28e301ef30a87ff3cd6527 and fixed in 5.15.54 with commit 4c0bb583a4444cce224e8661090cbffc98e2fe07
	Issue introduced in 4.4 with commit c3cdd6e48e35b7a02f28e301ef30a87ff3cd6527 and fixed in 5.17.2 with commit d2d9ebdbff79d87d27652578e6d1638ad3b5f3bf
	Issue introduced in 4.4 with commit c3cdd6e48e35b7a02f28e301ef30a87ff3cd6527 and fixed in 5.18 with commit c87b7b12f48db86ac9909894f4dc0107d7df6375

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-49285
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/iio/accel/mma8452.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/4c0bb583a4444cce224e8661090cbffc98e2fe07
	https://git.kernel.org/stable/c/d2d9ebdbff79d87d27652578e6d1638ad3b5f3bf
	https://git.kernel.org/stable/c/c87b7b12f48db86ac9909894f4dc0107d7df6375