Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2024-36972 high CVSS 7.8

Vulnerability in :linux_kernel: (CVE-2024-36972)

Summary

Vulnerability in :linux_kernel: (CVE-2024-36972). Successful exploitation can lead to full system takeover. Mitigation: upgrade to :2024-09-05 or later.

Original description

The description as published by the source.

In multiple functions of af_unix.c, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

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-36972 has been found in :linux_kernel:.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade :linux_kernel: to :2024-09-05 or later.
If unsure, ask your IT team or search ":linux_kernel: CVE-2024-36972" on the vendor's site.

CVE-2024-36972 (:linux_kernel:) — CWE-476 / CVSS v3 7.8
Attack vector: local / no user interaction
Patched: :2024-09-05 — 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 (CWE-476) exists in :linux_kernel:.

📍 Affected scope

Check the vendor advisory for the affected versions of :linux_kernel:.

🔥 Severity

Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to :2024-09-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・依存マニフェストで :linux_kernel: を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade :linux_kernel: to :2024-09-05

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

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

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

Affected packages

Android :linux_kernel:
[{"type":"ECOSYSTEM","events":[{"introduced":":0"},{"fixed":":2024-09-05"}]}]
Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.161"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.93"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.33"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.9.4"}]}]

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