Skip to main content

U-Boot EUVDEUVD-2026-89432

| CVE-2026-71974 MEDIUM
Out-of-bounds Write (CWE-787)
2026-09-29 VulnCheck GHSA-c7vr-vjm2-3grc
4.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain physical access to device
  2. Delivery
    Insert crafted boot media with oversized header
  3. Exploit
    read_slotted_partition() skips size validation
  4. Execution
    OOB write past load buffer into bootloader memory
  5. Impact
    Bootloader memory corruption / device compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires physical access to the device to supply crafted boot media (AV:P). Exploitation specifically targets U-Boot's Android boot method: the read_slotted_partition() function in boot/bootmeth_android.c reads an image size from the untrusted Android boot image header without validating it against the partition size, so an oversized header triggers the out-of-bounds write. Exploitation is LIMITED to devices that do NOT have Android Verified Boot (AVB) protection enabled - AVB-protected devices reject the tampered image and are not affected. Only U-Boot versions before 2026.10-rc3 using the Android bootmeth are vulnerable.

Impact

This is a genuine low-priority issue despite the OOB-write/memory-corruption classification. The vendor CVSS 4.0 vector (AV:P/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H) scoring 4.3 is dominated by the physical attack vector (AV:P) and the attack-requirement (AT:P), both of which sharply constrain real-world exploitability: an attacker must physically supply crafted boot media to the device. There is no EPSS score, no CISA KEV listing, and no public exploit code provided in the intelligence, which is consistent with a physically-gated bootloader flaw that does not lend itself to remote or automated mass exploitation. The impact is honestly capped at partial integrity (VI:L) and high availability (VA:H) - corrupting bootloader memory can brick or destabilize the device, but confidentiality impact is none (VC:N). A further limiting condition is that only devices lacking Android Verified Boot (AVB) protection are affected; AVB-enabled devices are not exploitable. All signals align: low CVSS, no exploitation evidence, physical prerequisite. This is a defense-in-depth hardening fix, not an urgent patch priority, except for threat models that explicitly include evil-maid / supply-chain physical tampering of boot media.

Exploit ScenarioDerived

An attacker with physical possession of a device (e.g., evil-maid or a compromised supply chain) crafts boot media containing an Android boot image with an oversized header declaring an image larger than its partition. When U-Boot's read_slotted_partition() loads it without bounds-checking, the read writes past the load buffer into bootloader memory, corrupting execution state. No public exploit code was identified in the provided intelligence; exploitation requires the target device to lack Android Verified Boot protection.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 29, 2026

An out-of-bounds write in U-Boot's Android boot method (boot/bootmeth_android.c) lets someone with physical access to a device boot from crafted media whose boot image header declares a size larger than the containing partition, causing U-Boot to write past its load buffer into bootloader memory before 2026.10-rc3. Only devices that actually use the Android bootmeth and do NOT have Android Verified Boot (AVB) enabled are exposed, since AVB rejects the tampered image; authentication requirements are not confirmed from available data, but the assessed vector is CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H and there is no public exploit identified at time of analysis, nor any CISA KEV listing. The practical risk is low-priority: exploitation is gated on physical possession of the device plus an unprotected boot chain, and impact is limited to integrity and availability of the bootloader rather than confidentiality or a remote attack path.

RemediationAI

Vendor-released patch: U-Boot 2026.10-rc3 fixes this issue (upstream fix commit 35432ef6fe2c79ab72709966e64815a45eb55c76, discussed on the list at https://patch.msgid.link/20260729-b4-android-bootmeth-oob-v1-1-31c3450ae0be@byteray.co.uk); upgrade to 2026.10-rc3 or later, or backport that commit's partition.size bounds check into the read_slotted_partition() path. Where upgrading immediately is not possible, the strongest compensating control is enabling Android Verified Boot with signed boot images, which causes AVB-protected devices to reject the crafted image entirely - at the cost of provisioning signing keys and a verified boot chain, and it does nothing for devices that cannot support AVB. Alternatively, build U-Boot without the Android boot method (or otherwise avoid read_slotted_partition() for untrusted media), which removes the vulnerable parsing path but also removes Android boot image support on that platform. Physical controls such as disabling removable-media boot, locking bootloader entry, and enforcing secure-boot/fuse policies reduce the AV:P attack surface but are operational mitigations rather than fixes. Full details are in the VulnCheck advisory at https://www.vulncheck.com/advisories/u-boot-before-2026.10-rc3-out-of-bounds-write-via-android-bootmeth-partition-read.

Affected VersionsENISA

U-Boot 0 <2026.10-rc3

Affected Packages

euvd u_boot fix: 2026.10-rc3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

U-Boot implements an 'Android boot method' in boot/bootmeth_android.c that locates and loads Android boot images from slotted (A/B) partitions. The helper read_slotted_partition() derives the number of blocks to read (num_blks) from the image size field in the Android boot image header - data that originates from untrusted boot media rather than from the bootloader's own configuration. Because the size was never checked against the size of the partition that holds the image, an oversized header causes the read/load to run past the end of the destination buffer, a classic CWE-787 out-of-bounds write into adjacent bootloader memory. The upstream fix commit 35432ef6fe2c79ab72709966e64815a45eb55c76 adds a bounds check comparing num_blks against partition.size and returns -EFBIG ('image larger than partition') when the header claims an image larger than its container, with a comment explicitly noting that the image size comes from the untrusted boot image header. The affected CPE, cpe:2.3:a:u-boot:u-boot:*:*:*:*:*:*:*:*, covers all U-Boot releases prior to 2026.10-rc3; the vulnerable code path in v2026.07 is visible at boot/bootmeth_android.c#L356. Memory corruption here affects the bootloader itself rather than a running OS, so it manifests as a boot-time integrity/availability failure and is only reachable when the Android boot method is compiled in and used and the device lacks Android Verified Boot enforcement.

Know when U Boot gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 4.3 MEDIUM
CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
vuln.today AI 5.2 MEDIUM

Physical boot-media access (AV:P) with low complexity and no auth/UI; bootloader memory corruption yields partial integrity (I:L) and high availability (A:H) impact, no confidentiality loss.

3.1 AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
4.0 AV:P/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE 4.8 MEDIUM
AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Physical
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Ubiquitous
U-Boot is the de facto bootloader across embedded/IoT and Android devices
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

More in U Boot

View all
CVE-2022-34835 CRITICAL POC
9.8 Jun 30

In Das U-Boot through 2022.07-rc5, an integer signedness error and resultant stack-based buffer overflow in the "i2c md"

CVE-2022-30790 HIGH POC
7.8 Jun 08

Das U-Boot 2022.01 has a Buffer Overflow, a different issue than CVE-2022-30552. Rated high severity (CVSS 7.8), this vu

CVE-2020-10648 HIGH POC
7.8 Mar 19

Das U-Boot through 2020.01 allows attackers to bypass verified boot restrictions and subsequently boot arbitrary images

CVE-2022-30767 CRITICAL POC
9.8 May 16

nfs_lookup_reply in net/nfs.c in Das U-Boot through 2022.04 (and through 2022.07-rc2) has an unbounded memcpy with a fai

CVE-2018-18439 CRITICAL POC
9.8 Nov 20

DENX U-Boot through 2018.09-rc1 has a remotely exploitable buffer overflow via a malicious TFTP server because TFTP traf

CVE-2022-2347 HIGH POC
7.7 Sep 23

There exists an unchecked length field in UBoot. Rated high severity (CVSS 7.7), this vulnerability is no authentication

CVE-2019-14199 CRITICAL
9.8 Jul 31

An issue was discovered in Das U-Boot through 2019.07. Rated critical severity (CVSS 9.8), this vulnerability is remotel

CVE-2019-14193 CRITICAL
9.8 Jul 31

An issue was discovered in Das U-Boot through 2019.07. Rated critical severity (CVSS 9.8), this vulnerability is remotel

CVE-2019-14203 CRITICAL
9.8 Jul 31

An issue was discovered in Das U-Boot through 2019.07. Rated critical severity (CVSS 9.8), this vulnerability is remotel

CVE-2019-14202 CRITICAL
9.8 Jul 31

An issue was discovered in Das U-Boot through 2019.07. Rated critical severity (CVSS 9.8), this vulnerability is remotel

CVE-2019-14201 CRITICAL
9.8 Jul 31

An issue was discovered in Das U-Boot through 2019.07. Rated critical severity (CVSS 9.8), this vulnerability is remotel

CVE-2019-14200 CRITICAL
9.8 Jul 31

An issue was discovered in Das U-Boot through 2019.07. Rated critical severity (CVSS 9.8), this vulnerability is remotel

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Micro 5.3 Not-Affected
SUSE Linux Enterprise Micro 5.4 Not-Affected
SUSE Linux Enterprise Micro 5.5 Not-Affected
SUSE Linux Enterprise Module for Basesystem 15 SP7 Not-Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy