This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2024-53192 →

UBUNTU-CVE-2024-53192

Vulnerability in linux-hwe-edge (UBUNTU-CVE-2024-53192)

Summary

Vulnerability in linux-hwe-edge (UBUNTU-CVE-2024-53192). Risk of unauthorized operations or information disclosure. Exploitable via hws. Mitigation: upgrade to 6.11.0-1015.15 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: clk: clk-loongson2: Fix potential buffer overflow in flexible-array member access Flexible-array member hws in struct clk_hw_onecell_data is annotated with the counted_by() attribute. This means that when memory is allocated for this array, the counter, which in this case is member num in the flexible structure, should be set to the maximum number of elements the flexible array can contain, or fewer. In this case, the total number of elements for the flexible array is determined by variable clks_num when allocating heap space via devm_kzalloc(), as shown below: 289 struct loongson2_clk_provider *clp; ... 296 for (p = data; p->name; p++) 297 clks_num++; 298 299 clp = devm_kzalloc(dev, struct_size(clp, clk_data.hws, clks_num), 300 GFP_KERNEL); So, clp->clk_data.num should be set to clks_num or less, and not exceed clks_num, as is currently the case. Otherwise, if data is written into clp->clk_data.hws[clks_num], the instrumentation provided by the compiler won't detect the overflow, leading to a memory corruption bug at runtime. Fix this issue by setting clp->clk_data.num to clks_num.

Source: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2024-53192 has been found in linux-hwe-edge.
Attackers can target a specific entry point like hws over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade linux-hwe-edge to 6.11.0-1015.15 or later.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2024-53192" on the vendor's site.

UBUNTU-CVE-2024-53192 (linux-hwe-edge)
Attack vector: local / no user interaction
Attack surface: hws / num / clks_num
Patched: 6.11.0-1015.15 — 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 linux-hwe-edge. Attackers reach the vulnerable code path via hws.

📍 Affected scope

Check the vendor advisory for the affected versions of linux-hwe-edge. Attack surface: hws / num / clks_num.

🔥 Severity

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

🔧 How to fix

Update to 6.11.0-1015.15.

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