Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-71972 Overview
CVE-2026-71972 is an out-of-bounds write vulnerability in Das U-Boot, a widely deployed open-source bootloader for embedded systems. The flaw resides in the video_display_rle8_bitmap function within drivers/video/video_bmp.c. Attackers can craft a malicious RLE8-compressed BMP image that causes the decoder to write past the framebuffer boundary. This corrupts memory adjacent to the framebuffer and crashes the bootloader. The vulnerability affects U-Boot releases up to and including 2026.10-rc5. Because U-Boot ships on millions of embedded devices, routers, industrial controllers, and IoT hardware, the flaw has broad exposure across the embedded ecosystem. The issue is tracked under [CWE-787] (Out-of-bounds Write).
Critical Impact
A crafted BMP splash image processed during boot can corrupt memory next to the framebuffer, crash the bootloader, and prevent affected embedded devices from starting.
Affected Products
- Das U-Boot bootloader versions up to and including 2026.10-rc5
- Embedded systems and firmware images bundling the vulnerable video_bmp.c RLE8 decoder
- Devices that render user-supplied or attacker-controllable BMP splash screens during boot
Discovery Timeline
- 2026-09-29 - CVE-2026-71972 published to NVD
- 2026-09-29 - Last updated in NVD database
- Fix commit - U-Boot upstream commit 5201e83 bounds RLE8 decode writes to the framebuffer
Technical Details for CVE-2026-71972
Vulnerability Analysis
The vulnerability sits in U-Boot's BMP rendering path used to display boot splash images. The function video_display_rle8_bitmap decodes run-length-encoded (RLE8) BMP data directly into the framebuffer pointer fb. The original implementation trusted the run-length and offset values embedded in the BMP header without validating them against the framebuffer size. A crafted RLE8 stream can therefore instruct the decoder to write bytes at addresses beyond priv->fb + priv->fb_size. Because U-Boot runs with full memory privileges before the operating system loads, out-of-bounds writes can corrupt neighboring bootloader structures, heap metadata, or code regions. The immediate observed outcome is a bootloader crash, producing a denial-of-service condition on the target device.
Root Cause
The root cause is missing bounds checking during RLE8 decompression. The decoder walks the compressed bitmap using encoded run lengths and delta escapes but never verifies that each write falls inside the framebuffer window [fb_start, fb_end). Any RLE opcode that advances the write cursor past fb_end results in an out-of-bounds write, matching the classic [CWE-787] pattern.
Attack Vector
An attacker must supply a crafted BMP file to a device that processes it during boot. Delivery paths include tampered firmware update packages, malicious images placed on attached storage such as USB or SD cards, or network-provisioned splash screens on adjacent-network provisioning flows. Successful exploitation crashes the bootloader and prevents the device from starting. The current advisory describes availability impact; the memory corruption primitive could warrant further research into code-execution reachability on specific platforms.
// Upstream fix in drivers/video/video_bmp.c
// video: bmp: bound RLE8 decode writes to the framebuffer
-static void video_display_rle8_bitmap(struct udevice *dev,
- struct bmp_image *bmp, uint bpix,
- struct bmp_color_table_entry *palette,
- uchar *fb, int x_off, int y_off,
- ulong width, ulong height)
+static int video_display_rle8_bitmap(struct udevice *dev,
+ struct bmp_image *bmp, uint bpix,
+ struct bmp_color_table_entry *palette,
+ uchar *fb, int x_off, int y_off,
+ ulong width, ulong height)
{
struct video_priv *priv = dev_get_uclass_priv(dev);
+ uchar *fb_start = priv->fb;
+ uchar *fb_end = (uchar *)priv->fb + priv->fb_size;
uchar *bmap;
ulong cnt, runlen;
int x, y;
Source: U-Boot commit 5201e83. The patch converts the function to return an int status and records fb_start and fb_end bounds so each RLE opcode can be validated before writing.
Detection Methods for CVE-2026-71972
Indicators of Compromise
- Repeated boot failures, watchdog resets, or hangs on the U-Boot splash screen after firmware or storage media changes
- Unexpected BMP files placed on boot partitions, EFI system partitions, or attached USB or SD media
- Firmware update artifacts containing modified splash.bmp or similarly named boot logo files
Detection Strategies
- Inventory devices running U-Boot and identify builds at or below 2026.10-rc5 using firmware version banners or build metadata
- Statically scan firmware images for the vulnerable video_display_rle8_bitmap symbol before the fix commit 5201e83
- Validate BMP splash files in build pipelines by fuzzing the RLE8 decoder or rejecting BMPs whose decoded pixel count exceeds framebuffer dimensions
Monitoring Recommendations
- Alert on unexpected modifications to boot partitions, splash image files, and firmware update packages in device management platforms
- Log and review boot-time crash signatures collected by remote device telemetry to spot patterns consistent with bootloader corruption
- Track upstream U-Boot advisories and the VulnCheck U-Boot Advisory for related decoder issues
How to Mitigate CVE-2026-71972
Immediate Actions Required
- Rebuild affected firmware from a U-Boot tree that includes commit 5201e83 and redeploy to affected devices
- Restrict physical and adjacent-network access to devices that accept external BMP splash images through USB, SD, or provisioning services
- Verify integrity of splash images shipped inside firmware packages and reject any BMPs from untrusted sources
Patch Information
The upstream fix is delivered by commit 5201e83342d64c2f438ea35158575f28225e752e in the U-Boot repository. The patch bounds every RLE8 decode write to the range [priv->fb, priv->fb + priv->fb_size) and changes video_display_rle8_bitmap to return a status code so callers can abort rendering on malformed input. Downstream vendors should cherry-pick this commit into vendor U-Boot forks and ship updated firmware. See the vulnerable source at drivers/video/video_bmp.c#L126 for context.
Workarounds
- Disable BMP splash rendering in U-Boot configuration by removing CONFIG_VIDEO_BMP_RLE8 and related splash options where feature loss is acceptable
- Ship only known-good, build-time signed splash images and disallow runtime replacement from user-accessible storage
- Enable secure boot and signed firmware update mechanisms so attacker-supplied BMPs cannot reach the vulnerable decoder
# Disable RLE8 BMP support in U-Boot defconfig to eliminate the vulnerable code path
# Edit configs/<board>_defconfig and remove or unset:
# CONFIG_VIDEO_BMP_RLE8=y
# CONFIG_SPLASH_SCREEN=y
scripts/config --file configs/<board>_defconfig --disable VIDEO_BMP_RLE8
scripts/config --file configs/<board>_defconfig --disable SPLASH_SCREEN
make <board>_defconfig
make -j$(nproc)
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

