LiveActive security incident?Get immediate response
CVE Record

CVE-2022-20239: remap_pfn_range' here may map out of size kernel memory (for example, may map the kernel area), and because...

remap_pfn_range' here may map out of size kernel memory (for example, may map the kernel area), and because the 'vma->vm_page_prot' can also be controlled by userspace, so userspace may map the kernel area to be writable, which is easy to be exploitedProduct: AndroidVersions: Android SoCAndroid ID: A-233972091

MediumCVSS 4.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-20239 is an Android SoC vulnerability where memory mapping behavior could expose kernel memory in an unsafe way. The public record rates it medium severity. Business urgency is mainly for organizations managing Android device fleets, especially devices that may not have received the August 2022 Android security updates.

Executive priority

Treat this as a fleet hygiene and patch assurance issue, not an emergency based on available evidence. Prioritize remediation where Android devices are business-critical, unmanaged, or behind on security patch levels.

Technical view

The record describes unsafe use of remap_pfn_range in Android SoC code. Userspace-controlled VMA page protections may allow mapping beyond intended memory size, potentially including writable kernel memory. The CVSS 3.1 score is 4.2, with high attack complexity, low privileges required, and limited confidentiality and availability impact.

Likely exposure

Exposure is most likely on Android devices using affected Android SoC components that have not received the relevant August 2022 Android security bulletin fixes. The public bundle does not identify specific OEM models, chipsets, or downstream firmware builds.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not listed as KEV. The description suggests userspace influence over memory mapping, but public evidence here is limited and does not provide exploit status, affected device models, or proof-of-concept details.

Researcher notes

The public record is sparse and does not name specific SoCs or code commits. The key technical concern is userspace-controlled memory mapping protection around remap_pfn_range, with possible writable kernel memory exposure. Validate only through vendor advisories, patch metadata, and affected build information.

Mitigation direction

  • Review the Android August 2022 security bulletin for vendor guidance.
  • Confirm affected Android devices have current OEM security updates installed.
  • Prioritize managed devices with outdated Android security patch levels.
  • Check OEM or SoC vendor advisories for device-specific fix availability.

Validation and detection

  • Inventory Android devices and record security patch levels.
  • Identify devices using Android SoC components covered by the bulletin.
  • Compare device patch status against August 2022 or later updates.
  • Track OEM firmware availability for unsupported or lagging models.
Prepared
Confidence
medium
Sources
3

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 · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2022-20239 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.2 (3.1)
Known Exploited
No
Published

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

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
2Source links

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.2CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L1.62.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.2Medium
CVSS 3.1 vector shape for CVE-2022-20239Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAndroidAndroid SoCListed
Weakness

CWE details

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

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.