Skip to content
This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2025-21932 →
Unrated

Vulnerability in linux-hwe-edge

UBUNTU-CVE-2025-21932 First seen on SecPulse

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-2025-21932 has been found in linux-hwe-edge.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2025-21932" on the vendor's site.

UBUNTU-CVE-2025-21932 (linux-hwe-edge)
Attack vector: local / no user interaction
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.

Affected scope

Check the vendor advisory for the affected versions of linux-hwe-edge.

Severity

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

How to fix

Update to the patched release per vendor advisory.

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. 1
    Identify exposureidentify
    grep -r 'linux-hwe-edge' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で linux-hwe-edge を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Ubuntu:16.04:LTS linux-hwe-edge
All versions
—
Ubuntu:18.04:LTS linux-aws-5.0
All versions
—
Ubuntu:18.04:LTS linux-aws-5.3
All versions
—
Ubuntu:18.04:LTS linux-azure
All versions
—
Ubuntu:18.04:LTS linux-azure-5.3
All versions
—
Ubuntu:18.04:LTS linux-azure-edge
All versions
—
Ubuntu:18.04:LTS linux-gcp
All versions
—
Ubuntu:18.04:LTS linux-gcp-5.3
All versions
—
Ubuntu:18.04:LTS linux-gke-4.15
All versions
—
Ubuntu:18.04:LTS linux-gke-5.4
All versions
—
Ubuntu:18.04:LTS linux-gkeop-5.4
All versions
—
Ubuntu:18.04:LTS linux-hwe
All versions
—
Ubuntu:18.04:LTS linux-hwe-edge
All versions
—
Ubuntu:18.04:LTS linux-oem
All versions
—
Ubuntu:18.04:LTS linux-oracle-5.0
All versions
—
Ubuntu:18.04:LTS linux-oracle-5.3
All versions
—
Ubuntu:20.04:LTS linux-aws-5.11
All versions
—
Ubuntu:20.04:LTS linux-aws-5.13
All versions
—
Ubuntu:20.04:LTS linux-aws-5.8
All versions
—
Ubuntu:20.04:LTS linux-azure-5.11
All versions
—
Ubuntu:20.04:LTS linux-azure-5.13
All versions
—
Ubuntu:20.04:LTS linux-azure-5.8
All versions
—
Ubuntu:20.04:LTS linux-azure-fde
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.11
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.13
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.8
All versions
—
Ubuntu:20.04:LTS linux-gke
All versions
—
Ubuntu:20.04:LTS linux-gke-5.15
All versions
—
Ubuntu:20.04:LTS linux-gkeop
All versions
—
Ubuntu:20.04:LTS linux-gkeop-5.15
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.11
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.13
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.8
All versions
—
Ubuntu:20.04:LTS linux-intel-5.13
All versions
—
Ubuntu:20.04:LTS linux-oem-5.10
All versions
—
Ubuntu:20.04:LTS linux-oem-5.13
All versions
—
Ubuntu:20.04:LTS linux-oem-5.14
All versions
—
Ubuntu:20.04:LTS linux-oem-5.6
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.11
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.13
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.8
All versions
—
Ubuntu:20.04:LTS linux-raspi2
All versions
—
Ubuntu:20.04:LTS linux-riscv
All versions
—
Ubuntu:20.04:LTS linux-riscv-5.11
All versions
—
Ubuntu:20.04:LTS linux-riscv-5.8
All versions
—
Ubuntu:22.04:LTS linux-allwinner-5.19
All versions
—
Ubuntu:22.04:LTS linux-aws-5.19
All versions
—
Ubuntu:22.04:LTS linux-aws-6.2
All versions
—
Ubuntu:22.04:LTS linux-aws-6.5
All versions
—
Ubuntu:22.04:LTS linux-azure-5.19
All versions
—
Ubuntu:22.04:LTS linux-azure-6.2
All versions
—
Ubuntu:22.04:LTS linux-azure-6.5
All versions
—
Ubuntu:22.04:LTS linux-azure-fde-5.19
All versions
—
Ubuntu:22.04:LTS linux-azure-fde-6.2
All versions
—
Ubuntu:22.04:LTS linux-gcp-5.19
All versions
—
Ubuntu:22.04:LTS linux-gcp-6.2
All versions
—
Ubuntu:22.04:LTS linux-gcp-6.5
All versions
—
Ubuntu:22.04:LTS linux-hwe-5.19
All versions
—
Ubuntu:22.04:LTS linux-hwe-6.2
All versions
—
Ubuntu:22.04:LTS linux-hwe-6.5
All versions
—
Ubuntu:22.04:LTS linux-intel-iot-realtime
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-5.19
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-6.2
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-6.5
All versions
—
Ubuntu:22.04:LTS linux-nvidia-6.2
All versions
—
Ubuntu:22.04:LTS linux-nvidia-6.5
All versions
—
Ubuntu:22.04:LTS linux-oem-5.17
All versions
—
Ubuntu:22.04:LTS linux-oem-6.0
All versions
—
Ubuntu:22.04:LTS linux-oem-6.1
All versions
—
Ubuntu:22.04:LTS linux-oem-6.5
All versions
—
Ubuntu:22.04:LTS linux-oracle-6.5
All versions
—
Ubuntu:22.04:LTS linux-realtime
All versions
—
Ubuntu:22.04:LTS linux-riscv
All versions
—
Ubuntu:22.04:LTS linux-riscv-5.19
All versions
—
Ubuntu:22.04:LTS linux-riscv-6.5
All versions
—
Ubuntu:22.04:LTS linux-starfive-5.19
All versions
—
Ubuntu:22.04:LTS linux-starfive-6.2
All versions
—
Ubuntu:22.04:LTS linux-starfive-6.5
All versions
—
Ubuntu:24.04:LTS linux-raspi-realtime
All versions
—
Ubuntu:24.04:LTS linux-realtime
All versions
—
Original description The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: mm: abort vma_modify() on merge out of memory failure The remainder of vma_modify() relies upon the vmg state remaining pristine after a merge attempt. Usually this is the case, however in the one edge case scenario of a merge attempt failing not due to the specified range being unmergeable, but rather due to an out of memory error arising when attempting to commit the merge, this assumption becomes untrue. This results in vmg->start, end being modified, and thus the proceeding attempts to split the VMA will be done with invalid start/end values. Thankfully, it is likely practically impossible for us to hit this in reality, as it would require a maple tree node pre-allocation failure that would likely never happen due to it being 'too small to fail', i.e. the kernel would simply keep retrying reclaim until it succeeded. However, this scenario remains theoretically possible, and what we are doing here is wrong so we must correct it. The safest option is, when this scenario occurs, to simply give up the operation. If we cannot allocate memory to merge, then we cannot allocate memory to split either (perhaps moreso!). Any scenario where this would be happening would be under very extreme (likely fatal) memory pressure, so it's best we give up early. So there is no doubt it is appropriate to simply bail out in this scenario. However, in general we must if at all possible never assume VMG state is stable after a…

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details