CVE-2025-20989: Infoleak

Published Jun 4, 2025
·
Updated

Improper logging in fingerprint trustlet prior to SMR May-2025 Release 1 allows local privileged attackers to get a hmackey.

Affected Software

88 affected components
Samsung Android=13.0-smr-apr-2022-r1
Samsung Android=13.0-smr-apr-2023-r1
Samsung Android=13.0-smr-apr-2024-r1
Samsung Android=13.0-smr-apr-2025-r1
Samsung Android=13.0-smr-aug-2022-r1
Samsung Android=13.0-smr-aug-2023-r1
Samsung Android=13.0-smr-aug-2024-r1
Samsung Android=13.0-smr-dec-2021-r1
Samsung Android=13.0-smr-dec-2022-r1
Samsung Android=13.0-smr-dec-2023-r1
Samsung Android=13.0-smr-dec-2024-r1
Samsung Android=13.0-smr-feb-2022-r1
Samsung Android=13.0-smr-feb-2023-r1
Samsung Android=13.0-smr-feb-2024-r1
Samsung Android=13.0-smr-feb-2025-r1
Samsung Android=13.0-smr-jan-2022-r1
Samsung Android=13.0-smr-jan-2023-r1
Samsung Android=13.0-smr-jan-2024-r1
Samsung Android=13.0-smr-jan-2025-r1
Samsung Android=13.0-smr-jul-2022-r1
Samsung Android=13.0-smr-jul-2023-r1
Samsung Android=13.0-smr-jul-2024-r1
Samsung Android=13.0-smr-jun-2022-r1
Samsung Android=13.0-smr-jun-2023-r1
Samsung Android=13.0-smr-jun-2024-r1
Samsung Android=13.0-smr-mar-2022-r1
Samsung Android=13.0-smr-mar-2023-r1
Samsung Android=13.0-smr-mar-2024-r1
Samsung Android=13.0-smr-mar-2025-r1
Samsung Android=13.0-smr-may-2022-r1
Samsung Android=13.0-smr-may-2023-r1
Samsung Android=13.0-smr-may-2024-r1
Samsung Android=13.0-smr-nov-2021-r1
Samsung Android=13.0-smr-nov-2022-r1
Samsung Android=13.0-smr-nov-2023-r1
Samsung Android=13.0-smr-nov-2024-r1
Samsung Android=13.0-smr-oct-2022-r1
Samsung Android=13.0-smr-oct-2023-r1
Samsung Android=13.0-smr-oct-2024-r1
Samsung Android=13.0-smr-sep-2022-r1
Samsung Android=13.0-smr-sep-2023-r1
Samsung Android=13.0-smr-sep-2024-r1
Samsung Android=14.0-smr-apr-2022-r1
Samsung Android=14.0-smr-apr-2023-r1
Samsung Android=14.0-smr-apr-2024-r1
Samsung Android=14.0-smr-apr-2025-r1
Samsung Android=14.0-smr-aug-2022-r1
Samsung Android=14.0-smr-aug-2023-r1
Samsung Android=14.0-smr-aug-2024-r1
Samsung Android=14.0-smr-dec-2021-r1
Samsung Android=14.0-smr-dec-2022-r1
Samsung Android=14.0-smr-dec-2023-r1
Samsung Android=14.0-smr-dec-2024-r1
Samsung Android=14.0-smr-feb-2022-r1
Samsung Android=14.0-smr-feb-2023-r1
Samsung Android=14.0-smr-feb-2024-r1
Samsung Android=14.0-smr-feb-2025-r1
Samsung Android=14.0-smr-jan-2022-r1
Samsung Android=14.0-smr-jan-2023-r1
Samsung Android=14.0-smr-jan-2024-r1
Samsung Android=14.0-smr-jan-2025-r1
Samsung Android=14.0-smr-jul-2022-r1
Samsung Android=14.0-smr-jul-2023-r1
Samsung Android=14.0-smr-jul-2024-r1
Samsung Android=14.0-smr-jun-2022-r1
Samsung Android=14.0-smr-jun-2023-r1
Samsung Android=14.0-smr-jun-2024-r1
Samsung Android=14.0-smr-mar-2022-r1
Samsung Android=14.0-smr-mar-2023-r1
Samsung Android=14.0-smr-mar-2024-r1
Samsung Android=14.0-smr-mar-2025-r1
Samsung Android=14.0-smr-may-2022-r1
Samsung Android=14.0-smr-may-2023-r1
Samsung Android=14.0-smr-may-2024-r1
Samsung Android=14.0-smr-nov-2021-r1
Samsung Android=14.0-smr-nov-2022-r1
Samsung Android=14.0-smr-nov-2023-r1
Samsung Android=14.0-smr-nov-2024-r1
Samsung Android=14.0-smr-oct-2022-r1
Samsung Android=14.0-smr-oct-2023-r1
Samsung Android=14.0-smr-oct-2024-r1
Samsung Android=14.0-smr-sep-2022-r1
Samsung Android=14.0-smr-sep-2023-r1
Samsung Android=14.0-smr-sep-2024-r1
Samsung Android=15.0-smr-apr-2025-r1
Samsung Android=15.0-smr-feb-2025-r1
Samsung Android=15.0-smr-jan-2025-r1
Samsung Android=15.0-smr-mar-2025-r1

Event History

Jun 4, 2025
CVE Published
via MITRE·04:56 AM
Data Sourced
via MITRE·04:56 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What level of access is required to exploit this issue?

An attacker needs local access plus high privileges, and exploitation has high attack complexity. The issue does not require user interaction.

2

Which systems should be prioritized for remediation?

The affected component is the fingerprint trustlet in Samsung Android software prior to SMR May-2025 Release 1. Systems updated to that release or later are not described as affected by the provided information.

3

What could an attacker obtain or affect?

Successful exploitation can expose an HMAC key through improper logging. The listed impact includes high confidentiality impact and low integrity and availability impact.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203