Vulnerability in intel-ucode (ALPINE-CVE-2025-35973)
Summary
Vulnerability in intel-ucode (ALPINE-CVE-2025-35973). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 20260812-r0 or later.
Original description
The description as published by the source.
Improper handling of values for some Intel(R) Processors within Ring 0: Kernel, Hypervisor and Bare Metal OS may allow an escalation of privilege. Authorized adversary with a privileged user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and require no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.
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 ALPINE-CVE-2025-35973 has been found in intel-ucode.
Risk of unauthorized operations or information disclosure.
What to do: upgrade intel-ucode to 20260812-r0 or later.
If unsure, ask your IT team or search "intel-ucode ALPINE-CVE-2025-35973" on the vendor's site.
ALPINE-CVE-2025-35973 (intel-ucode)
Patched: 20260812-r0 — 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 intel-ucode.
Check the vendor advisory for the affected versions of intel-ucode.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 20260812-r0.
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 'intel-ucode' . 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 'intel-ucode' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
intel-ucodeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade intel-ucode to 20260812-r0ステージング環境で 20260812-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security.alpinelinux.org