Vulnerability in Kernel (CVE-2024-53193)

Summary

Vulnerability in Kernel (CVE-2024-53193). Successful exploitation can lead to full system takeover. Exploitable via hws. Mitigation: upgrade to 6.11.11, 6.12.2 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 memory corruption bug in struct loongson2_clk_provider

Some heap space is allocated for the flexible structure struct clk_hw_onecell_data and its flexible-array member hws through
the composite structure struct loongson2_clk_provider in function
loongson2_clk_probe(), 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);

Then some data is written into the flexible array:

350 clp->clk_data.hws[p->id] = hw;

This corrupts clk_lock, which is the spinlock variable immediately
following the clk_data member in struct loongson2_clk_provider:

struct loongson2_clk_provider {
void __iomem *base;
struct device dev;
struct clk_hw_onecell_data clk_data;
spinlock_t clk_lock; / protect access to DIV registers */
};

The problem is that the flexible structure is currently placed in the
middle of struct loongson2_clk_provider instead of at the end.

Fix this by moving struct clk_hw_onecell_data clk_data; to the end of
struct loongson2_clk_provider. Also, add a code comment to help
prevent this from happening again in case new members are added to the
structure in the future.

This change also fixes the following -Wflex-array-member-not-at-end
wa…

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

CVE-2024-53193 (Kernel)
Attack vector: local / no user interaction
Attack surface: hws / clk_lock / clk_data
Patched: 6.11.11, 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 hws.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: hws / clk_lock / clk_data.

🔥 Severity

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

🔧 How to fix

Update to 6.11.11, 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.11.11, 6.12.2
```
ステージング環境で 6.11.11, 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.10.0"},{"fixed":"6.11.11"}]},{"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-53193 linux-lts Fixed in: 6.12.41-r0
Debian DEBIAN-CVE-2024-53193 linux Fixed in: 6.12.3-1