CVE-2025-20892: Medium severity samsung android vulnerability
Published Feb 4, 2025
·Updated
Protection Mechanism Failure in bootloader prior to SMR Jan-2025 Release 1 allows physical attackers to allow to execute fastboot command. User interaction is required for triggering this vulnerability.
Affected Software
78 affected components
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-20892?
CVE-2025-20892 has a medium severity rating as it requires user interaction to exploit.
2
How do I fix CVE-2025-20892?
To fix CVE-2025-20892, users should update to the latest Samsung Android release after the SMR Jan-2025 Release 1.
3
What versions of Samsung Android are affected by CVE-2025-20892?
CVE-2025-20892 affects Samsung Android versions 13.0 and 14.0 prior to the SMR Jan-2025 Release 1.
4
What causes CVE-2025-20892?
CVE-2025-20892 is caused by a protection mechanism failure in the bootloader that allows physical attackers to execute fastboot commands.
5
Is user interaction necessary for exploiting CVE-2025-20892?
Yes, user interaction is required to trigger the vulnerability described in CVE-2025-20892.