Kernel-address prediction via unused hardware RNG output
Published Jul 7, 2026 · Updated Jul 7, 2026
Insufficient entropy in Raspberry Pi 5 and Compute Module 5 rpi-eeprom before 28.22-1 allows local users to predict kernel addresses. The Pi 5 bootsys code enables the hardware RNG but historically failed to use its output for Device Tree rng-seed and kaslr-seed properties. Local access is required; the predictable values bypass KASLR as a defense against exploitation of another flaw, while weak RNG seeding can reduce random-number quality or delay boot.
Summary
What happened
Insufficient entropy in Raspberry Pi 5 and Compute Module 5 rpi-eeprom before 28.22-1 allows local users to predict kernel addresses. The Pi 5 bootsys code enables the hardware RNG but historically failed to use its output for Device Tree rng-seed and kaslr-seed properties. Local access is required; the predictable values bypass KASLR as a defense against exploitation of another flaw, while weak RNG seeding can reduce random-number quality or delay boot.
The record
- CVE
- CVE-2026-13199
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Vendor
- Raspberry Pi
- Product
- rpi-eeprom
- Classifications
- CWE-331, CAPEC-59
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2026CVE publishedPublication date reported by the CVE source.
- Jul 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <28.22-1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo