CVE-2025-20888: High severity libsthmbc vulnerability

Published Feb 4, 2025
·
Updated

Out-of-bounds write in handling the block size for smp4vtd 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-20888?

CVE-2025-20888 is considered a high severity vulnerability due to its potential for local attackers to execute arbitrary code with privileges.

2

How do I fix CVE-2025-20888?

To fix CVE-2025-20888, upgrade libsthmbc to SMR Jan-2025 Release 1 or later.

3

Who is affected by CVE-2025-20888?

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

4

What kind of attack does CVE-2025-20888 facilitate?

CVE-2025-20888 allows local attackers to execute arbitrary code through an out-of-bounds write vulnerability.

5

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

Yes, user interaction is required to trigger the exploit of CVE-2025-20888.

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