CVE-2021-25369
An improper access control vulnerability in sec_log file prior to SMR MAR-2021 Release 1 exposes sensitive kernel information to userspace.
- CVSS
- 6.2Mediumscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 8 Nov 2022CISA deadline for US federal agencies: 29 Nov 2022
- EPSS
- 1.1%chance of exploitation in the next 30 daystop 35% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 26 Mar 2021analysed here 12 Nov 2026
Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Samsung Mobile Samsung Mobile Devices | >= O(8.x), P(9.0), Q(10.0) and < SMR Mar-2021 Release 1Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- samsung:android
Fix and mitigation
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: response filtering
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 8 Nov 2022.
- CISA due date
- 29 Nov 2022, the remediation deadline for US federal agencies
- CISA required action
- Apply updates per vendor instructions.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation active, automatable no, technical impact partialAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 26 Mar 2021Published
- 8 Nov 2022Added to CISA KEV (exploited in the wild)591 days (about 2 years) later
- 29 Nov 2022CISA remediation due date (US federal agencies)21 days later
- 4 Feb 2025CISA SSVC assessment: exploitation active799 days (about 2 years) later
- 21 Oct 2025CVE record last updated259 days (about 9 months) later
- 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
| Metric | Value | What it means |
|---|---|---|
| Attack vector | LocalLocal access required (shell, logged-in user). | Local access required (shell, logged-in user). |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | NoneNo unauthorised modification. | No unauthorised modification. |
| Availability | NoneThe service stays up. | The service stays up. |
Common questions
Is CVE-2021-25369 being exploited?
Yes. CVE-2021-25369 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2021-25369?
CVE-2021-25369 is rated Medium with a CVSS score of 6.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2021-25369?
Yes. A fix has been recorded for CVE-2021-25369. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2021-25369 affect?
CVE-2021-25369 affects samsung:android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
3 references in the CVE record, grouped by the tags the record gives them.
Other links (3)
- security.samsungmobile.com /securityUpdate.smsb
- security.samsungmobile.com
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-25369
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.