Vulnerability in Kernel (CVE-2024-50005)

Summary

Vulnerability in Kernel (CVE-2024-50005). Risk of unauthorized operations or information disclosure. Exploitable via mac802154_scan_worker. Mitigation: upgrade to 6.6.55, 6.10.14, 6.11.3 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved:

mac802154: Fix potential RCU dereference issue in mac802154_scan_worker

In the mac802154_scan_worker function, the scan_req->type field was
accessed after the RCU read-side critical section was unlocked. According
to RCU usage rules, this is illegal and can lead to unpredictable
behavior, such as accessing memory that has been updated or causing
use-after-free issues.

This possible bug was identified using a static analysis tool developed
by myself, specifically designed to detect RCU-related issues.

To address this, the scan_req->type value is now stored in a local
variable scan_req_type while still within the RCU read-side critical
section. The scan_req_type is then used after the RCU lock is released,
ensuring that the type value is safely accessed without violating RCU
rules.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

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-50005 has been found in Kernel.
Attackers can target a specific entry point like mac802154_scan_worker over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 6.6.55, 6.10.14, 6.11.3 or later.
If unsure, ask your IT team or search "Kernel CVE-2024-50005" on the vendor's site.

CVE-2024-50005 (Kernel)
Attack surface: mac802154_scan_worker / scan_req_type
Patched: 6.6.55, 6.10.14, 6.11.3 — apply immediately
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 (unclassified) exists in Kernel. Attackers reach the vulnerable code path via mac802154_scan_worker.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: mac802154_scan_worker / scan_req_type.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 6.6.55, 6.10.14, 6.11.3.

🛡️ 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 'Kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

1
Identify exposure identify
```
grep -r 'Kernel' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kernel を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Kernel to 6.6.55, 6.10.14, 6.11.3
```
ステージング環境で 6.6.55, 6.10.14, 6.11.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"6.5.0"},{"fixed":"6.6.55"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.10.14"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.11.0"},{"fixed":"6.11.3"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2024-50005 linux Fixed in: 6.11.4-1