CVE-2026-13199 in EEPROM Firmware
Summary
by MITRE • 07/07/2026
EEPROM firmware on Raspberry Pi 5 and Compute Module 5 devices produced non-random KASLR and RNG seed values. This resulted in consistent kernel addresses across boots and devices, potentially making it easier to exploit other vulnerabilities. Additionally, the low-quality RNG seed may affect the quality of random numbers or delay booting while sufficient entropy is accumulated from other sources.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 07/07/2026
This vulnerability affects the bootloader and early boot process of raspberry pi 5 and compute module 5 devices where the embedded eeprom firmware generates predictable kernel address space layout randomization kaslr and random number generator rng seed values. the flaw stems from insufficient entropy sources during the device initialization phase, creating deterministic behavior that undermines fundamental security protections designed to prevent exploitation of memory layout vulnerabilities. the consistent kernel addresses across different boots and devices creates a persistent attack surface where adversaries can reliably predict memory locations for privilege escalation or code execution exploits. this vulnerability directly relates to weakness in random number generation as defined by cwe 330 and represents a failure in proper entropy collection during system initialization processes.
the technical implementation of the eeprom firmware fails to adequately gather sufficient entropy from hardware sources such as thermal noise, electrical interference, or other unpredictable environmental factors that would normally contribute to true randomness. this deterministic approach to seed generation creates predictable sequences that can be reverse engineered or brute-forced by attackers with access to multiple device instances or extended observation periods. the impact extends beyond simple kaspel protection degradation since the weak rng seeds may also affect cryptographic operations, session key generation, and other security-critical functions that depend on high-quality randomness. when the system attempts to initialize random number generators for various security services, it encounters insufficient entropy sources that can cause delays in boot processes while waiting for adequate entropy accumulation from alternative hardware sources.
the operational consequences of this vulnerability are significant for raspberry pi 5 and compute module 5 deployments where persistent security is required. attackers can leverage the predictable memory layouts to craft more effective exploits against other vulnerabilities present in the kernel or applications running on these devices. this weakness essentially provides a consistent foothold for exploitation that would otherwise require extensive reconnaissance or multiple successful attempts to overcome entropy-based protections. the vulnerability also impacts system availability since the boot process may experience delays while waiting for sufficient entropy, potentially creating denial of service conditions during critical system initialization phases. this issue aligns with attack techniques described in the mitre att&ck framework under initial access and privilege escalation tactics where predictable memory layouts enable more reliable exploitation of other security weaknesses.
mitigation strategies should focus on updating eeprom firmware to implement proper entropy collection mechanisms and ensure adequate randomness generation during boot processes. system administrators should monitor for device updates from raspberry pi foundation that address the underlying firmware issues, while also implementing additional security controls such as kernel lockdown modes and enhanced memory protection features. organizations deploying these devices in security-sensitive environments should consider implementing additional entropy sources or hardware random number generators to supplement the limited capabilities of the onboard eeprom firmware. regular vulnerability assessments should include checks for predictable memory layouts and randomness quality to identify potential exploitation vectors that may have been enabled by this flaw in the early boot process.