Fix trigger reference counting in iio: mma8452

Kernel Updated 02 Oct 2025

Summary

19/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002384: iio: mma8452: Fix trigger reference couting. Affects Kernel versions >= ae6d9ce05691bf79694074db7c7da980080548af, < fb75cc4740d81264cd5bcb0e17d961d018a8be96. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The iio: mma8452 is a driver in the Linux Kernel that provides support for the MMA8452 accelerometer sensor. This sensor is commonly used in various devices to measure acceleration. The driver allows applications to interact with the sensor and retrieve acceleration data. However, a vulnerability has been discovered in the driver's trigger reference counting mechanism.

Vulnerability Detail

The vulnerability in the iio: mma8452 driver lies in its trigger reference counting implementation. Due to a coding error, the driver does not properly handle the reference counting of triggers, which can lead to use-after-free vulnerabilities. An attacker could exploit this vulnerability by triggering the use-after-free condition, potentially leading to arbitrary code execution or a system crash. The vulnerability was introduced in version v4.2 of the Linux Kernel and has been fixed in version v4.9.293.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel.

Conclusion

The iio: mma8452 driver in the Linux Kernel is vulnerable to a trigger reference counting issue, which can lead to use-after-free vulnerabilities. To mitigate this vulnerability, it is recommended to update the Linux Kernel to version v4.9.293 or later. This update includes a fix for the trigger reference counting issue. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability in the iio: mma8452 driver could potentially allow an attacker to execute arbitrary code or crash the system.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the playground will analyze it for vulnerabilities.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

The only known mitigation for this vulnerability is to update the Linux Kernel to version v4.9.293 or later. Applying this update will patch the vulnerability and protect the system.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback