Vulnerability in Kernel (CVE-2024-50156)

Summary

Vulnerability in Kernel (CVE-2024-50156). Risk of unauthorized operations or information disclosure. Exploitable via dump_addr. Mitigation: upgrade to 5.15.170, 6.1.115, 6.6.59, 6.11.6 or later.

Original description

The description as published by the source.

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

drm/msm: Avoid NULL dereference in msm_disp_state_print_regs()

If the allocation in msm_disp_state_dump_regs() failed then
block->state can be NULL. The msm_disp_state_print_regs() function
does have code to try to handle it with:

if (*reg)
dump_addr = *reg;

...but since "dump_addr" is initialized to NULL the above is actually
a noop. The code then goes on to dereference dump_addr.

Make the function print "Registers not stored" when it sees a NULL to
solve this. Since we're touching the code, fix
msm_disp_state_print_regs() not to pointlessly take a double-pointer
and properly mark the pointer as const.

Patchwork: https://patchwork.freedesktop.org/patch/619657/

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

CVE-2024-50156 (Kernel)
Attack vector: local / no user interaction
Attack surface: dump_addr / const
Patched: 5.15.170, 6.1.115, 6.6.59, 6.11.6 — 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 dump_addr.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: dump_addr / const.

🔥 Severity

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

🔧 How to fix

Update to 5.15.170, 6.1.115, 6.6.59, 6.11.6.

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

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"5.14.0"},{"fixed":"5.15.170"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.115"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.59"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.11.6"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2024-50156 linux Fixed in: 6.1.115-1
Ubuntu UBUNTU-CVE-2024-50156 linux-hwe-edge