Vulnerability in Kernel (CVE-2024-49916)
Summary
Vulnerability in Kernel (CVE-2024-49916). Risk of unauthorized operations or information disclosure. Exploitable via dcn401_init_hw. Mitigation: upgrade to 6.11.3 or later.
Original description
The description as published by the source.
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Add NULL check for clk_mgr and clk_mgr->funcs in dcn401_init_hw
This commit addresses a potential null pointer dereference issue in the
dcn401_init_hw function. The issue could occur when dc->clk_mgr or
dc->clk_mgr->funcs is null.
The fix adds a check to ensure dc->clk_mgr and dc->clk_mgr->funcs is
not null before accessing its functions. This prevents a potential null
pointer dereference.
Reported by smatch:
drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn401/dcn401_hwseq.c:416 dcn401_init_hw() error: we previously assumed 'dc->clk_mgr' could be null (see line 225)
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-49916 has been found in Kernel.
Attackers can target a specific entry point like dcn401_init_hw over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 6.11.3 or later.
If unsure, ask your IT team or search "Kernel CVE-2024-49916" on the vendor's site.
CVE-2024-49916 (Kernel)
Attack surface: dcn401_init_hw
Patched: 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.
A vulnerability (unclassified) exists in Kernel. Attackers reach the vulnerable code path via dcn401_init_hw.
Check the vendor advisory for the affected versions of Kernel. Attack surface: dcn401_init_hw.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.11.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'Kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Kernelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Kernel to 6.11.3ステージング環境で 6.11.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2024-49916 linux
- Ubuntu UBUNTU-CVE-2024-49916 linux
References
- advisory github.com
- advisory nvd.nist.gov
- package git.kernel.org
- web git.kernel.org
- web git.kernel.org