What is the severity of CVE-2022-26097?

CVE-2022-26097 is classified as a high-severity vulnerability due to the potential for out of bounds write by a remote attacker.

How do I fix CVE-2022-26097?

To fix CVE-2022-26097, you should update your affected Android device to the latest security patch released after SMR Apr-2022.

Which versions of Android are affected by CVE-2022-26097?

CVE-2022-26097 affects Android versions 10.0, 11.0, and 12.0.

What kind of attacks can exploit CVE-2022-26097?

CVE-2022-26097 can be exploited by remote attackers to perform out of bounds write operations.

Is CVE-2022-26097 being actively exploited?

As of now, there are no confirmed reports indicating that CVE-2022-26097 is actively being exploited in the wild.

Vulnerability/
CVE-2022-26097

critical

9.8

CWE

476

11/4/2022

3/8/2024

CVE-2022-26097: Null Pointer Dereference

First published: Mon Apr 11 2022(Updated: )

Null pointer dereference vulnerability in parser_unknown_property function in libsimba library prior to SMR Apr-2022 Release 1 allows out of bounds write by remote attacker.

Credit: mobile.security@samsung.com

Affected Software	Affected Version	How to fix
Google Android	=10.0
Google Android	=11.0
Google Android	=12.0

Never miss a vulnerability like this again

Reference Links

https://security.samsungmobile.com/securityUpdate.smsb?year=2022&month=4

Frequently Asked Questions

What is the severity of CVE-2022-26097?
CVE-2022-26097 is classified as a high-severity vulnerability due to the potential for out of bounds write by a remote attacker.
How do I fix CVE-2022-26097?
To fix CVE-2022-26097, you should update your affected Android device to the latest security patch released after SMR Apr-2022.
Which versions of Android are affected by CVE-2022-26097?
CVE-2022-26097 affects Android versions 10.0, 11.0, and 12.0.
What kind of attacks can exploit CVE-2022-26097?
CVE-2022-26097 can be exploited by remote attackers to perform out of bounds write operations.
Is CVE-2022-26097 being actively exploited?
As of now, there are no confirmed reports indicating that CVE-2022-26097 is actively being exploited in the wild.

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

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-26097?
CVE-2022-26097 is classified as a high-severity vulnerability due to the potential for out of bounds write by a remote attacker.
How do I fix CVE-2022-26097?
To fix CVE-2022-26097, you should update your affected Android device to the latest security patch released after SMR Apr-2022.
Which versions of Android are affected by CVE-2022-26097?
CVE-2022-26097 affects Android versions 10.0, 11.0, and 12.0.
What kind of attacks can exploit CVE-2022-26097?
CVE-2022-26097 can be exploited by remote attackers to perform out of bounds write operations.
Is CVE-2022-26097 being actively exploited?
As of now, there are no confirmed reports indicating that CVE-2022-26097 is actively being exploited in the wild.