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-74221 Overview
CVE-2026-74221 is a buffer overflow vulnerability in Das U-Boot bootloader versions before 2026.10-rc5. The flaw resides in the nfs_readlink_reply() function inside net/nfs-common.c and is triggered while processing responses from a Network File System (NFS) server. A malicious NFS server can send crafted READLINK replies containing negative or oversized symbolic link length values. These values bypass validation and corrupt memory during bootloader execution. The vulnerability is classified under CWE-195: Signed to Unsigned Conversion Error and affects devices that use U-Boot's NFS boot functionality.
Critical Impact
A rogue or compromised NFS server on the boot network can corrupt U-Boot memory, crash the bootloader, and disrupt the boot chain on affected embedded and IoT devices.
Affected Products
- Das U-Boot bootloader versions prior to 2026.10-rc5
- Embedded systems and IoT devices using U-Boot NFS network boot
- Firmware images that build U-Boot with NFS client support enabled
Discovery Timeline
- 2026-09-29 - CVE-2026-74221 published to the National Vulnerability Database (NVD)
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-74221
Vulnerability Analysis
The vulnerability exists in the nfs_readlink_reply() function in net/nfs-common.c. This function parses NFS READLINK responses that return the target path of a symbolic link. The original code declared the symlink length field rlen as a signed int and used it without bounding against the receive buffer size.
When a malicious NFS server returns a READLINK reply with a very large or negative length value, subsequent memory operations read or write past the intended destination buffer. Because U-Boot runs before any operating system with minimal memory protections, out-of-bounds writes corrupt adjacent bootloader structures. The result is memory corruption and a bootloader crash during network boot, which produces an availability impact on the boot process.
Root Cause
The root cause is improper validation of a length value received over the network combined with a signed-to-unsigned integer conversion issue [CWE-195]. The signed int rlen allowed negative values to pass sanity checks and later be interpreted as very large unsigned sizes in memcpy-style operations.
Attack Vector
An attacker must control an NFS server that a target U-Boot device contacts during network boot, or must be positioned to intercept and rewrite NFS traffic on the boot network. No authentication or user interaction is required. The exploit is delivered as a crafted READLINK reply during the NFS boot sequence.
// Security patch in net/nfs-common.c
// Source: https://github.com/u-boot/u-boot/commit/1c0aff3a5fbfeee7a8948f624e0b8554e6e0d8fd
static int nfs_readlink_reply(uchar *pkt, unsigned int len)
{
struct rpc_t rpc_pkt;
- int rlen;
+ u32 rlen;
+ size_t data_offset;
int nfsv3_data_offset = 0;
memcpy((unsigned char *)&rpc_pkt, pkt, len);
The patch changes rlen from a signed int to an unsigned u32 and introduces a data_offset variable to bound the copy against the actual packet length. See the U-Boot commit for the full fix.
Detection Methods for CVE-2026-74221
Indicators of Compromise
- Repeated U-Boot boot failures or reboots on devices configured for NFS network boot.
- Console output showing memory corruption messages, aborts, or hangs immediately after an NFS READLINK request.
- Unexpected NFS servers responding to boot requests on the provisioning VLAN.
Detection Strategies
- Inspect U-Boot version strings across the fleet and flag any build older than 2026.10-rc5 that has NFS client support compiled in.
- Monitor NFS traffic on boot networks for READLINK replies whose declared symlink length exceeds a reasonable bound (for example, PATH_MAX) or is negative when interpreted as signed.
- Correlate boot log anomalies with the source IP of the responding NFS server to identify rogue endpoints.
Monitoring Recommendations
- Log all DHCP, TFTP, and NFS transactions on provisioning networks and alert on unauthorized servers answering boot requests.
- Baseline expected boot durations and alert when devices reboot in loops or fail to complete the NFS boot handoff.
- Capture packet traces from the boot VLAN periodically to enable retrospective analysis of malformed NFS replies.
How to Mitigate CVE-2026-74221
Immediate Actions Required
- Upgrade U-Boot to version 2026.10-rc5 or later and reflash affected devices at the next maintenance window.
- Restrict the network segment used for NFS boot to trusted infrastructure only and block untrusted hosts from answering NFS requests.
- Where possible, switch temporarily from NFS boot to a signed image boot method until patched firmware is deployed.
Patch Information
The fix is available in upstream U-Boot commit 1c0aff3a5fbfeee7a8948f624e0b8554e6e0d8fd, which bounds the length of the NFS readlink reply and changes the length type from signed int to unsigned u32. Additional context is available in the VulnCheck advisory and the U-Boot GitHub repository.
Workarounds
- Disable NFS boot support in U-Boot builds by removing CONFIG_CMD_NFS where NFS boot is not strictly required.
- Enforce Layer 2 isolation and 802.1X authentication on the boot VLAN to prevent unauthorized NFS servers from responding.
- Use static IP configuration and pin the expected NFS server address in U-Boot environment variables to reduce the attack window.
# Rebuild U-Boot without NFS client support (example)
scripts/config --file .config --disable CMD_NFS
scripts/config --file .config --disable NET_TCP
make olddefconfig
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

