CVE-2021-25369: Samsung Mobile Devices Improper Access Control
Samsung Mobile Devices · listed in the CISA catalog of actively exploited vulnerabilities since 2022-11-08.
- CVSS v3.1 (CVE record)
- 6.2
- medium
- EPSS (exploit probability, 30 days)
- 1.1%
- higher than 67% of all CVEs
- Added to CISA KEV
- 2022-11-08
- US federal due date 2022-11-29
- Automatable (CISA SSVC)
- no
- technical impact: partial
CVE-2021-25369 explained
CVE-2021-25369 is an improper access control vulnerability in the sec_log file on Samsung Mobile Devices. It exposes sensitive kernel information to userspace. CISA lists it as known to be exploited, so unpatched devices should be updated.
Impact
A local attacker can read sensitive kernel information that should not be available to userspace. No privileges or user interaction are required, and attack complexity is low. The impact is limited to confidentiality, with no direct effect on integrity or availability. CISA rates the technical impact as partial and the attack as not automatable. Attackers are known to exploit this vulnerability.
Who is affected
The CVE record lists Samsung Mobile Devices as affected with the version entry ≥ O(8.x), P(9.0), Q(10.0), < SMR Mar-2021 Release 1. This covers the listed Android branches before the March 2021 Samsung security maintenance release. The fix is included in SMR Mar-2021 Release 1.
Written with AI from the data on this page and checked against it automatically.
Official description
An improper access control vulnerability in sec_log file prior to SMR MAR-2021 Release 1 exposes sensitive kernel information to userspace.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Samsung Mobile DevicesAffectedFixed in
- ≥ O(8.x), P(9.0), Q(10.0), < SMR Mar-2021 Release 1
- SMR Mar-2021 Release 1
| Product | Affected | Fixed in |
|---|---|---|
| Samsung Mobile Devices |
|
|
How to fix it
- Update to a fixed version: SMR Mar-2021 Release 1.
- Vendor advisory: security.samsungmobile.com/securityUpdate.smsb
- CISA's deadline for US federal agencies: 2022-11-29 (passed) – a useful benchmark for everyone else, too.
What to do
- Update affected Samsung Mobile Devices to
SMR Mar-2021 Release 1or a later security maintenance release. - Follow the Samsung vendor advisory, in line with CISA's required action to apply updates per vendor instructions.
- Use device management tools to find devices still below
SMR Mar-2021 Release 1and enforce updates. - Restrict installation of untrusted apps, since the vulnerability is exploited locally on the device.
- Replace devices that can no longer receive Samsung security updates.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Partial – limited control or information
Weakness: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Questions about CVE-2021-25369
- Is CVE-2021-25369 exploited in the wild?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-11-08, with a US federal due date of 2022-11-29. Whether it has been used in ransomware campaigns is unknown.
- Which update fixes this vulnerability?
- The CVE record names
SMR Mar-2021 Release 1as the fixed version. Devices with this or a later security maintenance release are not affected. - Can it be exploited remotely?
- No. The attack vector is local, so an attacker needs code running on the device. No privileges or user interaction are required, and the result is disclosure of kernel information.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.