CVE-2025-20890: High severity libsthmbc vulnerability

Published Feb 4, 2025
·
Updated

Out-of-bounds write in decoding frame buffer in libsthmbc.so prior to SMR Jan-2025 Release 1 allows local attackers to execute arbitrary code with privilege. User interaction is required for triggering this vulnerability.

Affected Software

118 affected components
Unknown libsthmbc<SMR Jan-2025 Release 1
Samsung android=12.0
Samsung android=12.0-smr-apr-2022-r1
Samsung android=12.0-smr-apr-2023-r1
Samsung android=12.0-smr-apr-2024-r1
Samsung android=12.0-smr-aug-2022-r1
Samsung android=12.0-smr-aug-2023-r1
Samsung android=12.0-smr-aug-2024-r1
Samsung android=12.0-smr-dec-2021-r1
Samsung android=12.0-smr-dec-2022-r1
Samsung android=12.0-smr-dec-2023-r1
Samsung android=12.0-smr-dec-2024-r1
Samsung android=12.0-smr-feb-2022-r1
Samsung android=12.0-smr-feb-2023-r1
Samsung android=12.0-smr-feb-2024-r1
Samsung android=12.0-smr-jan-2022-r1
Samsung android=12.0-smr-jan-2023-r1
Samsung android=12.0-smr-jan-2024-r1
Samsung android=12.0-smr-jul-2022-r1
Samsung android=12.0-smr-jul-2023-r1
Samsung android=12.0-smr-jul-2024-r1
Samsung android=12.0-smr-jun-2022-r1
Samsung android=12.0-smr-jun-2023-r1
Samsung android=12.0-smr-jun-2024-r1
Samsung android=12.0-smr-mar-2022-r1
Samsung android=12.0-smr-mar-2023-r1
Samsung android=12.0-smr-mar-2024-r1
Samsung android=12.0-smr-may-2022-r1
Samsung android=12.0-smr-may-2023-r1
Samsung android=12.0-smr-may-2024-r1
Samsung android=12.0-smr-nov-2021-r1
Samsung android=12.0-smr-nov-2022-r1
Samsung android=12.0-smr-nov-2023-r1
Samsung android=12.0-smr-nov-2024-r1
Samsung android=12.0-smr-oct-2022-r1
Samsung android=12.0-smr-oct-2023-r1
Samsung android=12.0-smr-oct-2024-r1
Samsung android=12.0-smr-sep-2022-r1
Samsung android=12.0-smr-sep-2023-r1
Samsung android=12.0-smr_sep-2024-r1
Samsung android=13.0
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-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-jan-2022-r1
Samsung android=13.0-smr-jan-2023-r1
Samsung android=13.0-smr-jan-2024-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-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
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-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-jan-2022-r1
Samsung android=14.0-smr-jan-2023-r1
Samsung android=14.0-smr-jan-2024-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-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

Event History

Feb 4, 2025
CVE Published
via MITRE·07:19 AM
Data Sourced
via MITRE·07:19 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2025-20890?

CVE-2025-20890 has a high severity rating due to its potential for local attackers to execute arbitrary code.

2

How do I fix CVE-2025-20890?

To mitigate CVE-2025-20890, update to the SMR Jan-2025 Release 1 or later version of libsthmbc.

3

Who is affected by CVE-2025-20890?

CVE-2025-20890 affects users of libsthmbc versions prior to SMR Jan-2025 Release 1.

4

What type of vulnerability is CVE-2025-20890?

CVE-2025-20890 is an out-of-bounds write vulnerability specifically in the decoding frame buffer of libsthmbc.

5

Is user interaction required to exploit CVE-2025-20890?

Yes, user interaction is required to trigger the CVE-2025-20890 vulnerability.

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