CVE-2022-39120: CWE-120 Buffer Overflow in Unisoc (Shanghai) Technologies Co., Ltd. SC9863A/SC9832E/SC7731E/T610/T310/T606/T760/T610/T618/T606/T612/T616/T760/T770/T820/S8000
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
AI Analysis
Technical Summary
CVE-2022-39120 is a medium severity vulnerability identified in sensor drivers of several Unisoc (Shanghai) Technologies Co., Ltd. chipsets, including SC9863A, SC9832E, SC7731E, and multiple T-series models such as T610, T310, T606, T760, T618, T612, T616, T770, T820, and S8000. These chipsets are commonly integrated into Android devices running Android 10, 11, and 12. The vulnerability arises from a missing bounds check in the sensor driver code, leading to a potential out-of-bounds write condition. This is classified under CWE-120, which pertains to classic buffer overflow issues. Exploiting this flaw could allow a local attacker with limited privileges (low-level privileges) to cause a denial of service (DoS) by crashing the kernel, resulting in system instability or reboot. The CVSS v3.1 base score is 5.5, reflecting a medium severity level, with the attack vector being local (AV:L), requiring low attack complexity (AC:L), low privileges (PR:L), no user interaction (UI:N), and impacting availability only (A:H) without affecting confidentiality or integrity. No known exploits have been reported in the wild, and no patches were linked in the provided data, indicating that remediation may require vendor updates or firmware patches. The vulnerability's impact is limited to local denial of service rather than remote code execution or privilege escalation, but it still poses a risk to device stability and availability, especially in environments where device uptime is critical.
Potential Impact
For European organizations, the primary impact of CVE-2022-39120 lies in potential service disruptions caused by local denial of service on devices using affected Unisoc chipsets. Many low-cost or mid-range Android devices, particularly those using Unisoc SoCs, may be deployed in enterprise or industrial environments, including IoT devices, mobile endpoints, or embedded systems. A successful exploitation could lead to kernel crashes, forcing device reboots and causing temporary loss of availability. This can disrupt business operations, especially in sectors relying on continuous mobile device availability such as logistics, retail, healthcare, or field services. While the vulnerability does not allow remote exploitation or data compromise, the denial of service could be leveraged by malicious insiders or attackers with local access to degrade operational capabilities. Additionally, the lack of patches or updates might prolong exposure, increasing risk over time. Organizations with Bring Your Own Device (BYOD) policies or those using devices with Unisoc chipsets should be aware of this threat to avoid unexpected device failures.
Mitigation Recommendations
To mitigate CVE-2022-39120, European organizations should take a multi-layered approach: 1) Inventory and identify devices using affected Unisoc chipsets and Android versions (10, 11, 12). 2) Engage with device vendors and manufacturers to obtain firmware or OS updates that address this vulnerability once available. 3) Restrict local access to devices, limiting the ability of untrusted users or applications to execute code or interact with sensor drivers. 4) Implement mobile device management (MDM) solutions to enforce security policies, monitor device health, and remotely manage updates. 5) For critical environments, consider deploying endpoint protection solutions capable of detecting abnormal kernel crashes or device instability. 6) Educate users on the risks of installing untrusted applications or granting unnecessary permissions that could facilitate local exploitation. 7) Where possible, isolate devices with Unisoc chipsets from sensitive networks to reduce the impact of potential denial of service. 8) Monitor vendor advisories and security bulletins for patches or workarounds and apply them promptly. These steps go beyond generic advice by focusing on device-specific inventory, vendor coordination, and operational controls to reduce exposure.
Affected Countries
Germany, France, Italy, Spain, Poland, United Kingdom, Netherlands
CVE-2022-39120: CWE-120 Buffer Overflow in Unisoc (Shanghai) Technologies Co., Ltd. SC9863A/SC9832E/SC7731E/T610/T310/T606/T760/T610/T618/T606/T612/T616/T760/T770/T820/S8000
Description
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in kernel.
AI-Powered Analysis
Technical Analysis
CVE-2022-39120 is a medium severity vulnerability identified in sensor drivers of several Unisoc (Shanghai) Technologies Co., Ltd. chipsets, including SC9863A, SC9832E, SC7731E, and multiple T-series models such as T610, T310, T606, T760, T618, T612, T616, T770, T820, and S8000. These chipsets are commonly integrated into Android devices running Android 10, 11, and 12. The vulnerability arises from a missing bounds check in the sensor driver code, leading to a potential out-of-bounds write condition. This is classified under CWE-120, which pertains to classic buffer overflow issues. Exploiting this flaw could allow a local attacker with limited privileges (low-level privileges) to cause a denial of service (DoS) by crashing the kernel, resulting in system instability or reboot. The CVSS v3.1 base score is 5.5, reflecting a medium severity level, with the attack vector being local (AV:L), requiring low attack complexity (AC:L), low privileges (PR:L), no user interaction (UI:N), and impacting availability only (A:H) without affecting confidentiality or integrity. No known exploits have been reported in the wild, and no patches were linked in the provided data, indicating that remediation may require vendor updates or firmware patches. The vulnerability's impact is limited to local denial of service rather than remote code execution or privilege escalation, but it still poses a risk to device stability and availability, especially in environments where device uptime is critical.
Potential Impact
For European organizations, the primary impact of CVE-2022-39120 lies in potential service disruptions caused by local denial of service on devices using affected Unisoc chipsets. Many low-cost or mid-range Android devices, particularly those using Unisoc SoCs, may be deployed in enterprise or industrial environments, including IoT devices, mobile endpoints, or embedded systems. A successful exploitation could lead to kernel crashes, forcing device reboots and causing temporary loss of availability. This can disrupt business operations, especially in sectors relying on continuous mobile device availability such as logistics, retail, healthcare, or field services. While the vulnerability does not allow remote exploitation or data compromise, the denial of service could be leveraged by malicious insiders or attackers with local access to degrade operational capabilities. Additionally, the lack of patches or updates might prolong exposure, increasing risk over time. Organizations with Bring Your Own Device (BYOD) policies or those using devices with Unisoc chipsets should be aware of this threat to avoid unexpected device failures.
Mitigation Recommendations
To mitigate CVE-2022-39120, European organizations should take a multi-layered approach: 1) Inventory and identify devices using affected Unisoc chipsets and Android versions (10, 11, 12). 2) Engage with device vendors and manufacturers to obtain firmware or OS updates that address this vulnerability once available. 3) Restrict local access to devices, limiting the ability of untrusted users or applications to execute code or interact with sensor drivers. 4) Implement mobile device management (MDM) solutions to enforce security policies, monitor device health, and remotely manage updates. 5) For critical environments, consider deploying endpoint protection solutions capable of detecting abnormal kernel crashes or device instability. 6) Educate users on the risks of installing untrusted applications or granting unnecessary permissions that could facilitate local exploitation. 7) Where possible, isolate devices with Unisoc chipsets from sensitive networks to reduce the impact of potential denial of service. 8) Monitor vendor advisories and security bulletins for patches or workarounds and apply them promptly. These steps go beyond generic advice by focusing on device-specific inventory, vendor coordination, and operational controls to reduce exposure.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Unisoc
- Date Reserved
- 2022-09-01T00:00:00.000Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682cd0fb1484d88663aec6b3
Added to database: 5/20/2025, 6:59:07 PM
Last enriched: 7/6/2025, 11:27:46 AM
Last updated: 2/7/2026, 8:21:46 PM
Views: 37
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2110: Improper Restriction of Excessive Authentication Attempts in Tasin1025 SwiftBuy
MediumCVE-2026-2109: Improper Authorization in jsbroks COCO Annotator
MediumCVE-2026-2108: Denial of Service in jsbroks COCO Annotator
MediumCVE-2026-2107: Improper Authorization in yeqifu warehouse
MediumCVE-2026-2106: Improper Authorization in yeqifu warehouse
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.