← Back
CVE-2024-50302
CISA KEV
medium
CVSS 5.5
[KEV] Vulnerability in :linux_kernel: (CVE-2024-50302)
Summary
vulnerability in :linux_kernel: (CVE-2024-50302). Confidential information can be exposed externally. Listed in CISA KEV — actively exploited. Mitigation: upgrade to `:2025-03-05` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-50302** has been found in :linux_kernel:.
Confidential information can be exposed externally. CVSS score: 5.5/10.
Note: CISA has officially confirmed this is **actively exploited in the wild**. Treat it with elevated urgency.
What to do: upgrade :linux_kernel: to **:2025-03-05** or later.
If unsure, ask your IT team or search ":linux_kernel: CVE-2024-50302" on the vendor's site.
CVE-2024-50302 (:linux_kernel:) — CWE-908 / CVSS v3 5.5
Attack vector: local / no user interaction
Patched: `:2025-03-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-908) exists in :linux_kernel:.
📍 Affected scope
:linux_kernel: — .
🔥 Severity
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally **Listed in CISA KEV** — actively exploited in the wild, treat as top priority.
🔧 How to fix
Update to **:2025-03-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. Run `grep -r ':linux_kernel:' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r ':linux_kernel:' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `:linux_kernel:` を grep し、稼働しているサービス・バージョンを把握する。
-
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
6Apply patch patch
Upgrade :linux_kernel: to :2025-03-05ステージング環境で :2025-03-05 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Android
:linux_kernel:
[{"type":"ECOSYSTEM","events":[{"introduced":":0"},{"fixed":":2025-03-05"}]}]
References
- advisory 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- advisory 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
- advisory https://source.android.com/security/bulletin/2025-03-01
- mailing af854a3a-2127-422b-91ae-364da2661108
- mailing af854a3a-2127-422b-91ae-364da2661108
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- patch https://android.googlesource.com/kernel/common/+/f02dd268a08d4e7ec09ec0ddd2a861ab5a51a0ae
- patch https://android.googlesource.com/kernel/common/+/853ec04e2de45ae6d1fc9476ce52d06582ad87ed
- web https://nvd.nist.gov/vuln/detail/CVE-2024-50302
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://github.com/advisories/GHSA-9qwc-r24c-26j3