Vulnerability in linux-hwe-edge (UBUNTU-CVE-2025-21939)
Summary
Vulnerability in linux-hwe-edge (UBUNTU-CVE-2025-21939). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.11.0-1018.18~24.04.1 or later.
Original description
The description as published by the source.
In the Linux kernel, the following vulnerability has been resolved: drm/xe/hmm: Don't dereference struct page pointers without notifier lock The pnfs that we obtain from hmm_range_fault() point to pages that we don't have a reference on, and the guarantee that they are still in the cpu page-tables is that the notifier lock must be held and the notifier seqno is still valid. So while building the sg table and marking the pages accesses / dirty we need to hold this lock with a validated seqno. However, the lock is reclaim tainted which makes sg_alloc_table_from_pages_segment() unusable, since it internally allocates memory. Instead build the sg-table manually. For the non-iommu case this might lead to fewer coalesces, but if that's a problem it can be fixed up later in the resource cursor code. For the iommu case, the whole sg-table may still be coalesced to a single contigous device va region. This avoids marking pages that we don't own dirty and accessed, and it also avoid dereferencing struct pages that we don't own. v2: - Use assert to check whether hmm pfns are valid (Matthew Auld) - Take into account that large pages may cross range boundaries (Matthew Auld) v3: - Don't unnecessarily check for a non-freed sg-table. (Matthew Auld) - Add a missing up_read() in an error path. (Matthew Auld) (cherry picked from commit ea3e66d280ce2576664a862693d1da8fd324c317)
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-2025-21939 has been found in linux-hwe-edge.
Risk of unauthorized operations or information disclosure.
What to do: upgrade linux-hwe-edge to 6.11.0-1018.18~24.04.1 or later.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2025-21939" on the vendor's site.
UBUNTU-CVE-2025-21939 (linux-hwe-edge)
Attack vector: local / no user interaction
Patched: 6.11.0-1018.18~24.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.
A vulnerability (unclassified) exists in linux-hwe-edge.
Check the vendor advisory for the affected versions of linux-hwe-edge.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.11.0-1018.18~24.04.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'linux-hwe-edge' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
linux-hwe-edgeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade linux-hwe-edge to 6.11.0-1018.18~24.04.1ステージング環境で 6.11.0-1018.18~24.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report git.kernel.org