Vulnerability in linux-hwe-edge (UBUNTU-CVE-2025-37896)
Summary
Vulnerability in linux-hwe-edge (UBUNTU-CVE-2025-37896). Risk of unauthorized operations or information disclosure. Exploitable via write_cache. Mitigation: upgrade to 6.14.0-1009.9~24.04.1 or later.
Original description
The description as published by the source.
In the Linux kernel, the following vulnerability has been resolved: spi: spi-mem: Add fix to avoid divide error For some SPI flash memory operations, dummy bytes are not mandatory. For example, in Winbond SPINAND flash memory devices, the write_cache and update_cache operation variants have zero dummy bytes. Calculating the duration for SPI memory operations with zero dummy bytes causes a divide error when ncycles is calculated in the spi_mem_calc_op_duration(). Add changes to skip the 'ncylcles' calculation for zero dummy bytes. Following divide error is fixed by this change: Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI ... ? do_trap+0xdb/0x100 ? do_error_trap+0x75/0xb0 ? spi_mem_calc_op_duration+0x56/0xb0 ? exc_divide_error+0x3b/0x70 ? spi_mem_calc_op_duration+0x56/0xb0 ? asm_exc_divide_error+0x1b/0x20 ? spi_mem_calc_op_duration+0x56/0xb0 ? spinand_select_op_variant+0xee/0x190 [spinand] spinand_match_and_init+0x13e/0x1a0 [spinand] spinand_manufacturer_match+0x6e/0xa0 [spinand] spinand_probe+0x357/0x7f0 [spinand] ? kernfs_activate+0x87/0xd0 spi_mem_probe+0x7a/0xb0 spi_probe+0x7d/0x130
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-37896 has been found in linux-hwe-edge.
Attackers can target a specific entry point like write_cache over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade linux-hwe-edge to 6.14.0-1009.9~24.04.1 or later.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2025-37896" on the vendor's site.
UBUNTU-CVE-2025-37896 (linux-hwe-edge)
Attack vector: local / no user interaction
Attack surface: write_cache / update_cache / ncycles
Patched: 6.14.0-1009.9~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. Attackers reach the vulnerable code path via write_cache.
Check the vendor advisory for the affected versions of linux-hwe-edge. Attack surface: write_cache / update_cache / ncycles.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.14.0-1009.9~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.14.0-1009.9~24.04.1ステージング環境で 6.14.0-1009.9~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
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report git.kernel.org
- report git.kernel.org
- report git.kernel.org