First published: Tue Feb 04 2025(Updated: )
Out-of-bounds write in accessing uninitialized memory for svc1td 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.
Credit: mobile.security@samsung.com
Affected Software | Affected Version | How to fix |
---|---|---|
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-20882 is considered a high severity vulnerability due to its potential for local attackers to execute arbitrary code with privileges.
To fix CVE-2025-20882, you should update the libsthmbc library to a version released after SMR Jan-2025 Release 1.
CVE-2025-20882 affects users of the libsthmbc library prior to SMR Jan-2025 Release 1.
CVE-2025-20882 can be exploited by local attackers to execute arbitrary code, resulting in potential privilege escalation.
Yes, user interaction is required to trigger the exploitation of CVE-2025-20882.