CVE-2025-21080
Published Dec 2, 2025
·Updated
Improper export of android application components in Dynamic Lockscreen prior to SMR Dec-2025 Release 1 allows local attackers to access files with Dynamic Lockscreen's privilege.
Affected Software
16 affected components
Android Dynamic Lockscreen<SMR Dec-2025 Release 1
Samsung Android=15.0
Samsung Android=15.0-smr-apr-2025-r1
Samsung Android=15.0-smr-aug-2025-r1
Samsung Android=15.0-smr-jul-2025-r1
Samsung Android=15.0-smr-jun-2025-r1
Samsung Android=15.0-smr-mar-2025-r1
Samsung Android=15.0-smr-may-2025-r1
Samsung Android=15.0-smr-nov-2025-r1
Samsung Android=15.0-smr-oct-2025-r1
Samsung Android=15.0-smr-sep-2025-r1
Samsung Android=16.0
Samsung Android=16.0-smr-aug-2025-r1
Samsung Android=16.0-smr-nov-2025-r1
Samsung Android=16.0-smr-oct-2025-r1
Samsung Android=16.0-smr-sep-2025-r1
Event History
Dec 2, 2025
CVE Published
via MITRE·01:23 AM
Data Sourced
via MITRE·01:23 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 AM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-21080?
CVE-2025-21080 is considered a high-severity vulnerability due to its potential for local exploitation.
2
How do I fix CVE-2025-21080?
To fix CVE-2025-21080, update to the latest version of the Android Dynamic Lockscreen, specifically SMR Dec-2025 Release 1.
3
Who is affected by CVE-2025-21080?
CVE-2025-21080 affects users of the Android Dynamic Lockscreen prior to SMR Dec-2025 Release 1.
4
What are the potential impacts of CVE-2025-21080?
The potential impact of CVE-2025-21080 includes unauthorized access to files due to improper component export.
5
Is CVE-2025-21080 being actively exploited?
As of now, there have been no confirmed reports of active exploitation of CVE-2025-21080.