Out-of-Bounds Write in U-Boot (CVE-2026-71974)
Summary
Out-of-bounds write in U-Boot (CVE-2026-71974). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
U-Boot before 2026.10-rc3 contains an out-of-bounds write vulnerability in read_slotted_partition() that fails to validate image size against partition bounds. Attackers with physical access can supply crafted boot media with oversized headers to write past the load buffer into bootloader memory on devices without Android Verified Boot protection.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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 CVE-2026-71974 has been found in U-Boot.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "U-Boot CVE-2026-71974" on the vendor's site.
CVE-2026-71974 (U-Boot) — CWE-787 / CVSS v3 4.8
Attack vector: physical / unauthenticated / 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.
Out-of-bounds write (CWE-787) exists in U-Boot.
Check the vendor advisory for the affected versions of U-Boot.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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 'U-Boot' . 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 'U-Boot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
U-Bootを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-71974 u-boot
References
- web github.com
- web github.com
- web github.com
- web patch.msgid.link
- web vulncheck.com
- web nvd.nist.gov
- web github.com