Vulnerability in Kernel (CVE-2024-56695)

Summary

Vulnerability in Kernel (CVE-2024-56695). Successful exploitation can lead to full system takeover. Exploitable via kfd_get_cu_occupancy. Mitigation: upgrade to 6.12.2 or later.

Original description

The description as published by the source.

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

drm/amdkfd: Use dynamic allocation for CU occupancy array in 'kfd_get_cu_occupancy()'

The kfd_get_cu_occupancy function previously declared a large
cu_occupancy array as a local variable, which could lead to stack
overflows due to excessive stack usage. This commit replaces the static
array allocation with dynamic memory allocation using kcalloc,
thereby reducing the stack size.

This change avoids the risk of stack overflows in kernel space, in
scenarios where AMDGPU_MAX_QUEUES is large. The allocated memory is
freed using kfree before the function returns to prevent memory
leaks.

Fixes the below with gcc W=1:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c: In function ‘kfd_get_cu_occupancy’:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_process.c:322:1: warning: the frame size of 1056 bytes is larger than 1024 bytes [-Wframe-larger-than=]
322 | }
| ^

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-56695 has been found in Kernel.
Attackers can target a specific entry point like kfd_get_cu_occupancy over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade Kernel to 6.12.2 or later.
If unsure, ask your IT team or search "Kernel CVE-2024-56695" on the vendor's site.

CVE-2024-56695 (Kernel)
Attack vector: local / no user interaction
Attack surface: kfd_get_cu_occupancy / cu_occupancy / kcalloc / AMDGPU_MAX_QUEUES
Patched: 6.12.2 — 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 kfd_get_cu_occupancy.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: kfd_get_cu_occupancy / cu_occupancy / kcalloc / AMDGPU_MAX_QUEUES.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 6.12.2.

🛡️ 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.12.2
```
ステージング環境で 6.12.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.0"},{"fixed":"6.12.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

BellSoft Alpaquita BELL-CVE-2024-56695 linux-lts Fixed in: 6.12.41-r0