Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2021-0920 CISA KEV high

[KEV] Vulnerability in Android Kernel (CVE-2021-0920)

Summary

Vulnerability in Android Kernel (CVE-2021-0920). Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited. Mitigation: upgrade to :2021-11-05 or later.

Original description

The description as published by the source.

In unix_scm_to_skb of af_unix.c, there is a possible use after free bug due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

Source: CISA Known Exploited Vulnerabilities NVD CISA KEV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-0920 has been found in Android Kernel.
Risk of unauthorized operations or information disclosure.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: upgrade Android Kernel to :2021-11-05 or later.
If unsure, ask your IT team or search "Android Kernel CVE-2021-0920" on the vendor's site.

CVE-2021-0920 (Android Kernel) — CWE-362
Patched: :2021-11-05 — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-362) exists in Android Kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Android Kernel.

🔥 Severity

Severity: High. Risk of unauthorized operations or information disclosure. Listed in CISA KEV — actively exploited in the wild, treat as top priority.

🔧 How to fix

Update to :2021-11-05.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Android Kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Consider incident declaration escalate 
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 3
    Apply patch patch 
    Upgrade Android Kernel to :2021-11-05

    ステージング環境で :2021-11-05 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Android :linux_kernel:
[{"type":"ECOSYSTEM","events":[{"introduced":":0"},{"fixed":":2021-11-05"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details