Vulnerability in Linux Kernel (CVE-2024-50302, CVSS 5.5, KEV)

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.

Original description

The description as published by the source.

In hid_alloc_report_buf of hid-core.c, there is a possible leak of kernel memory contents to a USB HID due to uninitialized data. This could lead to physical information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Source: CISA Known Exploited Vulnerabilities NVD GitHub Advisory 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-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

Check the vendor advisory for the affected versions of 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. Audit SBOM/dependencies to find affected services.

Response actions

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

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Linux Kernel を使っているサービスとバージョンを洗い出す。
2
Consider incident declaration escalate
```
Notify SOC / on-call
```
CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
3
Apply patch patch
```
Upgrade Linux Kernel to :2025-03-05
```
ステージング環境で :2025-03-05 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
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":":2025-03-05"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2024-50302 linux Fixed in: 5.10.234-1
Ubuntu UBUNTU-CVE-2024-50302 linux Fixed in: 3.13.0-207.258

[KEV] Vulnerability in Linux Kernel (CVE-2024-50302)