CVE-2022-39105: Android Sensor Driver Out of Bounds Write Vulnerability

:unknown: Updated 02 Oct 2025

Summary

01/12/2022
Yes i
High
Not published

CVE-2022-39105: In sensor driver, there is a possible out of bounds write due to a missing bound check. This could lead to local denial of service in kernel. Affects :unknown: versions >= SoCVersion:0, < SoCVersion:2022-12-05. Fixed in SoCVersion:2022-12-05. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Android operating system is a widely used open-source platform that powers a variety of devices, including smartphones and tablets. It includes a range of drivers that facilitate communication between the hardware and software components. One such driver is the sensor driver, which manages data from various sensors (e.g., accelerometers, gyroscopes). This driver is crucial for enabling features like motion detection and orientation changes. However, a vulnerability has been identified in the sensor driver that could lead to severe security implications.

Vulnerability Detail

The vulnerability arises from a missing boundary check in the sensor driver, which allows for a possible out-of-bounds write. This flaw can be exploited locally, leading to a denial of service (DoS) condition within the kernel. The absence of proper checks means that an attacker could manipulate the driver to write data outside the allocated memory space, potentially causing system instability or crashes. This vulnerability is classified as having a high severity level and falls under the category of elevation of privilege (EoP).

How To Fix

Minimum fixed version

SoCVersion:2022-12-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds provided for this vulnerability. The best course of action is to apply the available patch as soon as possible to prevent potential exploitation.

Conclusion

In summary, CVE-2022-39105 is a critical vulnerability in the Android sensor driver that can lead to local denial of service due to an out-of-bounds write. Users are strongly encouraged to update their devices to the patched version released on December 5, 2022, to ensure their systems remain secure.

See every vulnerability recorded for :unknown: →

Share this vulnerability

FAQ

CVE-2022-39105 is a vulnerability in the Android sensor driver that allows for a possible out-of-bounds write due to a missing boundary check.

The vulnerability can lead to local denial of service in the kernel, causing system instability or crashes.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Yes, a patch is available as of December 5, 2022. It is recommended to update your device to this version to mitigate the risk.

If you cannot update your device, it is advisable to limit the use of applications that may exploit this vulnerability until a fix can be applied.

Related vulnerabilities

Recent vulnerabilities recorded for :unknown:.

How To Fix

Minimum fixed version

SoCVersion:2022-12-05

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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