Vulnerability · Published Feb 26, 2025 · Assigned by Linux

CVE-2022-49285iio: accel: mma8452: use the correct logic to get mma8452_data

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 18% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.3%top 82.4% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux5.17.3-1DEBIAN-CVE-2022-49285
Debian:13linux5.17.3-1DEBIAN-CVE-2022-49285
Debian:14linux5.17.3-1DEBIAN-CVE-2022-49285
Ubuntu:22.04:LTSlinux5.15.0-50.56UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-aws5.15.0-1021.25UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-azure5.15.0-1021.26UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1024.30.1UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-gcp5.15.0-1019.25UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-gke5.15.0-1017.20UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1004.6UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-ibm5.15.0-1015.17UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1017.22UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-kvm5.15.0-1019.23UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-50.56UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1015.15UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-oracle5.15.0-1019.24UBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-raspi5.15.0-1016.18UBUNTU-CVE-2022-49285
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2022-49285
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2022-49285

Affected products (as reported)

VendorProductVersions
Linux Linux c3cdd6e48e35b7a02f28e301ef30a87ff3cd6527 – before 4c0bb583a4444cce224e8661090cbffc98e2fe07c3cdd6e48e35b7a02f28e301ef30a87ff3cd6527 – before d2d9ebdbff79d87d27652578e6d1638ad3b5f3bfc3cdd6e48e35b7a02f28e301ef30a87ff3cd6527 – before c87b7b12f48db86ac9909894f4dc0107d7df6375
Linux Linux 4.4

References