LiveActive security incident?Get immediate response
CVE Record

CVE-2023-21492: Kernel pointers are printed in the log file prior to SMR May-2023 Release 1 allows a privileged local attac...

Kernel pointers are printed in the log file prior to SMR May-2023 Release 1 allows a privileged local attacker to bypass ASLR.

MediumCVSS 4.4Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Samsung Mobile issue can expose kernel memory addresses in log files. A local attacker with high privileges could use that information to weaken Android ASLR protections. The direct impact is information disclosure, but CISA KEV status raises urgency because exploitation has been reported.

Executive priority

Treat this as a priority mobile patching issue, not a standalone remote compromise. KEV status makes delayed remediation hard to justify, especially for managed Samsung fleets used by executives, administrators, or staff handling sensitive data.

Technical view

CVE-2023-21492 is a CWE-532 information exposure flaw in selected Samsung Android 11, 12, and 13 devices before SMR May-2023 Release 1. Kernel pointers are printed to logs, allowing a privileged local attacker to bypass ASLR. CVSS is 4.4 with local access and high privileges required.

Likely exposure

Exposure is limited to selected Samsung Mobile Devices on Android 11, 12, or 13 that have not received SMR May-2023 Release 1 or later. Risk is mainly enterprise-managed or personally owned Samsung devices with outdated security patch levels.

Exploitation context

CISA KEV inclusion supports known exploitation. The source bundle does not provide exploit details, scale, affected model list, or whether exploitation is targeted or widespread. The vulnerability requires local access and high privileges, so it is most concerning as part of a chained attack.

Researcher notes

The evidence identifies kernel pointer leakage to logs and ASLR bypass by a privileged local attacker. Public sources in the bundle do not name exact models, log locations, exploit chains, or detection indicators. Avoid assuming broader Android impact beyond selected Samsung devices.

Mitigation direction

  • Inventory Samsung Android 11, 12, and 13 devices in managed fleets.
  • Apply Samsung SMR May-2023 Release 1 or later where applicable.
  • Prioritize devices that remain before the May 2023 security release.
  • Follow Samsung guidance for device-specific update availability.
  • For unsupported devices, plan replacement or restrict high-privilege local access.

Validation and detection

  • Verify each Samsung device security patch level against May 2023 Release 1 or later.
  • Check MDM inventory for Samsung Android 11, 12, and 13 devices.
  • Confirm whether CVE-2023-21492 appears in Samsung’s May 2023 bulletin.
  • Track CISA KEV status and internal remediation deadlines.
  • Document exceptions for devices unable to receive the Samsung update.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-532: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-21492 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.4 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.4CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N0.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2023-21492Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Samsung MobileSamsung Mobile DevicesSelected Android 11, 12, 13 devicesListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-532 · source CWE mapping

Insertion of Sensitive Information into Log File

Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.