What is the severity of CVE-2022-32621?

CVE-2022-32621 is considered a high-severity vulnerability due to its potential to allow local escalation of privileges.

How do I fix CVE-2022-32621?

To fix CVE-2022-32621, apply the patch identified as ALPS07310829 provided by the vendor.

What types of devices are affected by CVE-2022-32621?

CVE-2022-32621 specifically affects devices running Android 12.0.

Is user interaction required to exploit CVE-2022-32621?

No, exploitation of CVE-2022-32621 does not require any user interaction.

What conditions allow the exploitation of CVE-2022-32621?

CVE-2022-32621 can be exploited due to a race condition leading to an out of bounds write.

Vulnerability/
CVE-2022-32621

medium

6.4

CWE

362 787

5/12/2022

24/4/2025

CVE-2022-32621: Race Condition

First published: Mon Dec 05 2022(Updated: )

In isp, there is a possible out of bounds write due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07310829; Issue ID: ALPS07310829.

Credit: security@mediatek.com

Affected Software	Affected Version	How to fix
Android	=12.0
MediaTek MT6895
MediaTek MT6983
All of
Android	=12.0
Any of
MediaTek MT6895
MediaTek MT6983

Never miss a vulnerability like this again

Reference Links

https://corp.mediatek.com/product-security-bulletin/December-2022

Frequently Asked Questions

What is the severity of CVE-2022-32621?
CVE-2022-32621 is considered a high-severity vulnerability due to its potential to allow local escalation of privileges.
How do I fix CVE-2022-32621?
To fix CVE-2022-32621, apply the patch identified as ALPS07310829 provided by the vendor.
What types of devices are affected by CVE-2022-32621?
CVE-2022-32621 specifically affects devices running Android 12.0.
Is user interaction required to exploit CVE-2022-32621?
No, exploitation of CVE-2022-32621 does not require any user interaction.
What conditions allow the exploitation of CVE-2022-32621?
CVE-2022-32621 can be exploited due to a race condition leading to an out of bounds write.

agent/type
agent/severity
agent/author
agent/references
agent/first-publish-date
agent/description
agent/event
agent/source
agent/weakness
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/mitre-cve
source/MITRE
agent/last-modified-date
collector/nvd-api
source/NVD
agent/software-canonical-lookup
vendor/google
canonical/android
version/android/12.0
vendor/mediatek
canonical/mediatek mt6895
canonical/mediatek mt6983

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-32621?
CVE-2022-32621 is considered a high-severity vulnerability due to its potential to allow local escalation of privileges.
How do I fix CVE-2022-32621?
To fix CVE-2022-32621, apply the patch identified as ALPS07310829 provided by the vendor.
What types of devices are affected by CVE-2022-32621?
CVE-2022-32621 specifically affects devices running Android 12.0.
Is user interaction required to exploit CVE-2022-32621?
No, exploitation of CVE-2022-32621 does not require any user interaction.
What conditions allow the exploitation of CVE-2022-32621?
CVE-2022-32621 can be exploited due to a race condition leading to an out of bounds write.