cve.bz

CVE-2026-71971 u-boot u-boot: Out-of-bounds Write

8.8 highEPSS 0.4%

High (8.8) in u-boot u-boot. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
U-Boot before 2026.10-rc3 with CONFIG_IP_DEFRAG enabled contains an out-of-bounds write vulnerability in the __net_defragment() function in net/net.c. Remote attackers can send a crafted IP fragment with non-zero offset and More-Fragments flag set during netboot to corrupt adjacent memory and crash the bootloader.

Severity

CVSS 4.0

8.8 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-71971 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71971?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71971?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71971 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
u-bootbefore 2026.10-rc3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14u-bootno fix listedDEBIAN-CVE-2026-71971
Ubuntu22.04:LTSu-boot2022.01+dfsg-2ubuntu2.8UBUNTU-CVE-2026-71971 USN-8884-1
Ubuntu22.04:LTS, 24.04:LTSu-boot-nezhano fix listedUBUNTU-CVE-2026-71971
Ubuntu24.04:LTSu-boot2025.10-0ubuntu0.24.04.3UBUNTU-CVE-2026-71971 USN-8884-1
Ubuntu26.04:LTSu-boot2025.10-0ubuntu2.1UBUNTU-CVE-2026-71971 USN-8884-1
Ubuntu26.10u-boot2025.10-0ubuntu5UBUNTU-CVE-2026-71971
UbuntuPro:16.04:LTSu-boot2016.01+dfsg1-2ubuntu5+esm1UBUNTU-CVE-2026-71971 USN-8884-1
UbuntuPro:18.04:LTSu-boot2020.10+dfsg-1ubuntu0~18.04.3+esm1UBUNTU-CVE-2026-71971 USN-8884-1
UbuntuPro:20.04:LTSu-boot2021.01+dfsg-3ubuntu0~20.04.6+esm1UBUNTU-CVE-2026-71971 USN-8884-1
Azure Linux3qemuno fix listedAZL-105711

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

References

Check your stackJSON