How to Fix CVE-2022-22265: Samsung Mobile Samsung Mobile Devices (Bundle Sibling)

By Sai Kiran Pandrala

CVE-2022-22265 ships in the same vendor advisory as CVE-2021-25487. The patched build at the primary write-up closes this CVE too.

What's different about CVE-2022-22265?

An improper check or handling of exceptional conditions in NPU driver prior to SMR Jan-2022 Release 1 allows arbitrary memory write and code execution.

The flaw class and remediation are identical to the primary CVE in the bundle. A successful exploit gives the attacker the impact described in the vendor advisory.

How to fix CVE-2022-22265

Apply the patched build documented in the primary write-up: How to Fix CVE-2021-25487. The vendor ships a single fix that covers every CVE in this advisory.

Frequently asked questions

Is CVE-2022-22265 actively exploited?

Yes. CVE-2022-22265 is on the CISA Known Exploited Vulnerabilities catalog, so federal civilian agencies are required to patch on the published deadline. Most enterprises treat the same date as the practical floor.

What is the CVSS severity of CVE-2022-22265?

Medium. See the advisory for the full CVSS vector.

Where can I read the official advisory?

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

Does the patch require a reboot?

It depends on the deployment. Service-only updates usually need a service restart; OS-level fixes require a full reboot. Check the vendor release notes for the exact post-upgrade steps.

References

• Official vendor advisory: https://security.samsungmobile.com/securityUpdate.smsb?year=2022&month=1
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-22265
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2021-25487

*This guide is part of the Samsung Mobile Samsung Mobile Devices bundle. Full remediation procedure is at CVE-2021-25487.*