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

UBUNTU-CVE-2024-43825

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

Summary

Vulnerability in linux-hwe-edge (UBUNTU-CVE-2024-43825). Successful exploitation can lead to full system takeover. Exploitable via new. Mitigation: upgrade to 6.8.0-1020.22~22.04.1 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: iio: Fix the sorting functionality in iio_gts_build_avail_time_table The sorting in iio_gts_build_avail_time_table is not working as intended. It could result in an out-of-bounds access when the time is zero. Here are more details: 1. When the gts->itime_table[i].time_us is zero, e.g., the time sequence is 3, 0, 1, the inner for-loop will not terminate and do out-of-bound writes. This is because once times[j] > new, the value new will be added in the current position and the times[j] will be moved to j+1 position, which makes the if-condition always hold. Meanwhile, idx will be added one, making the loop keep running without termination and out-of-bound write. 2. If none of the gts->itime_table[i].time_us is zero, the elements will just be copied without being sorted as described in the comment "Sort times from all tables to one and remove duplicates". For more details, please refer to https://lore.kernel.org/all/6dd0d822-046c-4dd2-9532-79d7ab96ec05@gmail.com.

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-43825 has been found in linux-hwe-edge.
Attackers can target a specific entry point like new over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade linux-hwe-edge to 6.8.0-1020.22~22.04.1 or later.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2024-43825" on the vendor's site.

UBUNTU-CVE-2024-43825 (linux-hwe-edge)
Attack vector: local / no user interaction
Attack surface: new
Patched: 6.8.0-1020.22~22.04.1 — 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 new.

📍 Affected scope

Check the vendor advisory for the affected versions of linux-hwe-edge. Attack surface: new.

🔥 Severity

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

🔧 How to fix

Update to 6.8.0-1020.22~22.04.1.

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