VulnerabilityPublished 20 Aug 2026Updated 27 Oct 2026

CVE-2025-21709: linux-raspi, linux-raspi-realtime vulnerabilities

Affects Linux kernelSource GCVE Database

Mentioned vulnerabilities

Not known to be exploited · fixed in 6.8.0-1061.65 : patch Linux kernel soon.

Data as of 28 Oct 2026, 05:11 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.8.0-1061.65, 6.8.0-2050.52

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

usn-8665-1

What to do

Upgrade the Ubuntu to 6.8.0-1061.65 (linux-raspi package) or 6.8.0-2050.52 (linux-raspi-realtime package).

Patches and advisories

ubuntu.com/security/notices/USN-8665-1 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Ubuntu 24.04 LTSlinux-raspi`pkg:deb/ubuntu/linux-raspi?arch=source&distro=noble`Other threats	Affected <6.8.0-1061.65	Fixed in 6.8.0-1061.65
Ubuntu Pro Realtime 24.04 LTSlinux-raspi-realtime`pkg:deb/ubuntu/linux-raspi-realtime?arch=source&distro=realtime/noble`Other threats	Affected <6.8.0-2050.52	Fixed in 6.8.0-2050.52

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied promptly. Update the linux-raspi and linux-raspi-realtime kernel packages to versions 6.8.0-1061.65 or 6.8.0-2050.52 or later as provided by the vendor. After updating, reboot the system to activate the fixes. Due to an ABI change, all third-party kernel modules must be recompiled and reinstalled to maintain compatibility. Follow the vendor's update instructions carefully to ensure full remediation.

Description

Multiple security vulnerabilities affecting the Linux kernel for Raspberry Pi systems were addressed in this update. These include speculative execution flaws in AMD processors that could expose sensitive information, issues in AMD Zen 2 processors that might allow privilege escalation, and entropy handling flaws in AMD Zen 5 processors affecting randomness quality. Additionally, numerous security issues across a wide range of Linux kernel subsystems and drivers were fixed. These vulnerabilities could potentially allow local attackers to compromise system integrity or confidentiality. The update requires a system reboot and recompilation of third-party kernel modules due to ABI changes.

Impact

Local attackers could exploit these vulnerabilities to expose sensitive information, escalate privileges, or compromise system integrity. The speculative execution flaws in AMD processors may lead to data leakage. The AMD Zen 2 processor issue could allow corruption of instructions at higher privilege levels, resulting in privilege escalation. The entropy handling flaw in AMD Zen 5 processors may cause loss of confidentiality and integrity due to insufficient randomness. The broad range of kernel subsystem fixes addresses multiple potential attack vectors that could compromise the system.

References

Community reviews

Loading reviews…