CVE-2025-20889: Medium severity libsthmbc vulnerability

Published Feb 4, 2025
·
Updated

Out-of-bounds read in decoding malformed bitstream for smp4vtd in libsthmbc.so prior to SMR Jan-2025 Release 1 allows local attackers to read arbitrary memory. 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-20889?

CVE-2025-20889 is classified as a high-severity vulnerability due to its potential for arbitrary memory reads.

2

How do I fix CVE-2025-20889?

To resolve CVE-2025-20889, update libsthmbc to the version available in SMR Jan-2025 Release 1 or later.

3

Who is affected by CVE-2025-20889?

Users of libsthmbc prior to SMR Jan-2025 Release 1 are vulnerable to CVE-2025-20889.

4

What kind of attack can exploit CVE-2025-20889?

CVE-2025-20889 can be exploited by local attackers who can trigger it through user interaction.

5

What does CVE-2025-20889 affect specifically?

CVE-2025-20889 specifically affects the decoding of malformed bitstreams in the smp4vtd component of libsthmbc.so.

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