LiveActive security incident?Get immediate response
CVE Record

CVE-2022-20372: In exynos5_i2c_irq of (TBD), there is a possible out of bounds write due to a use after free.

In exynos5_i2c_irq of (TBD), there is a possible out of bounds write due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-195480799References: N/A

HighCVSS 7.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-20372 is an Android kernel memory-safety flaw in exynos5_i2c_irq. The supplied description says it could allow local privilege escalation without user interaction, but exploitation requires existing local privileges, specifically System execution privileges per Android’s text.

Executive priority

Treat this as high priority for Android fleet patch governance, especially managed devices with sensitive data. Business urgency is driven by local privilege escalation impact, not remote wormability or confirmed exploitation.

Technical view

The issue is a use-after-free in exynos5_i2c_irq that may cause an out-of-bounds write. It is classified as CWE-416 and scored CVSS 7.3. The affected product is listed only as Android kernel, with Android bug ID A-195480799 and Pixel August 2022 bulletin reference.

Likely exposure

Exposure is most likely on Android kernel builds that contain the affected exynos5_i2c_irq code and have not received the relevant August 2022 security update or vendor backport. The bundle does not identify specific device models.

Exploitation context

The source bundle does not show known active exploitation, and KEV is false. Based on CVSS and Android’s description, this is local-only, low-complexity, no-user-interaction, and requires prior privileges; it is not described as remotely exploitable.

Researcher notes

Evidence is limited to the CVE record and Android Pixel bulletin reference. The function name points to kernel I2C interrupt handling, but the bundle does not provide a patch diff, affected device list, or exploit details.

Mitigation direction

  • Apply the relevant Android or device-vendor security update addressing CVE-2022-20372.
  • Check the Pixel August 2022 bulletin and OEM advisories for patch availability.
  • Prioritize Android kernel updates on devices using affected kernel code.
  • Retire or isolate devices that cannot receive vendor kernel fixes.

Validation and detection

  • Inventory Android devices and record kernel build and security patch level.
  • Confirm whether vendor firmware includes the CVE-2022-20372 or A-195480799 fix.
  • Review OEM security bulletins for model-specific applicability and backport status.
  • Verify fleet policy blocks outdated Android security patch levels where possible.
Prepared
Confidence
medium
Sources
3

Public sources used

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-416: 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-2022-20372 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
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2022-20372Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 kernelListed
Weakness

CWE details

CWE-416

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs