Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-66646: CWE-476: NULL Pointer Dereference in RIOT-OS RIOT

0
Low
VulnerabilityCVE-2025-66646cvecve-2025-66646cwe-476
Published: Wed Dec 17 2025 (12/17/2025, 19:18:08 UTC)
Source: CVE Database V5
Vendor/Project: RIOT-OS
Product: RIOT

Description

CVE-2025-66646 is a low-severity vulnerability in RIOT OS versions prior to 2025. 10, affecting the IPv6 fragmentation reassembly module. The flaw is a NULL pointer dereference triggered when a fragmented IPv6 packet with fragment offset 0 and an empty payload is received, causing the OS to crash and resulting in a denial of service (DoS). Exploitation requires the gnrc_ipv6_ext_frag module to be enabled and the attacker to send crafted IPv6 packets to the device. No authentication or user interaction is needed, but the impact is limited to DoS without data compromise. The vulnerability has a CVSS 4. 0 score of 1. 7, indicating low severity. European organizations using RIOT OS in IoT or embedded devices should update to version 2025. 10 to mitigate this issue.

AI-Powered Analysis

AILast updated: 12/24/2025, 20:47:14 UTC

Technical Analysis

CVE-2025-66646 is a vulnerability identified in the open-source RIOT OS, an operating system tailored for IoT and embedded devices. The issue resides in the IPv6 fragmentation reassembly implementation, specifically within the gnrc_ipv6_ext_frag module. When the system receives a fragmented IPv6 packet where the fragment offset is zero but the payload is empty, the payload pointer is set to NULL. Despite this, the code attempts to copy the payload into the reassembly buffer, leading to a NULL pointer dereference. This causes the operating system to crash, resulting in a denial of service condition. The vulnerability affects all RIOT OS versions prior to 2025.10, where the flaw has been fixed. Exploitation requires an attacker to send specially crafted IPv6 packets to the device, with no need for authentication or user interaction. The CVSS 4.0 score of 1.7 reflects the low impact, as the vulnerability only causes a crash without compromising confidentiality or integrity. No known exploits are currently in the wild. This vulnerability highlights the risks inherent in IPv6 packet processing in constrained IoT environments and the importance of robust input validation and error handling in embedded OS network stacks.

Potential Impact

For European organizations deploying RIOT OS in IoT devices, this vulnerability could lead to denial of service conditions on affected devices. While the impact is limited to availability and does not affect confidentiality or integrity, DoS in IoT devices can disrupt critical services, especially in industrial control systems, smart city infrastructure, and healthcare monitoring devices. The ability to remotely trigger the crash without authentication increases the risk in environments where devices are exposed to untrusted IPv6 networks. However, the low CVSS score and lack of known exploits suggest the threat is currently limited. Organizations relying heavily on RIOT OS for critical IoT deployments in Europe should consider the potential operational disruptions and prioritize patching to maintain service continuity.

Mitigation Recommendations

European organizations should immediately upgrade all RIOT OS deployments to version 2025.10 or later, where the vulnerability is patched. Network administrators should consider filtering or monitoring IPv6 fragmented packets, especially those with fragment offset zero and empty payloads, to detect or block suspicious traffic targeting the gnrc_ipv6_ext_frag module. Implementing network segmentation and limiting exposure of IoT devices to untrusted IPv6 networks can reduce attack surface. Additionally, organizations should audit their IoT device configurations to verify whether the vulnerable IPv6 fragmentation module is enabled and disable it if not required. Regular firmware and OS updates, combined with network-level anomaly detection tailored for IoT traffic patterns, will further mitigate risks from similar vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-05T20:23:19.595Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6943060a0b6f32e62bf23024

Added to database: 12/17/2025, 7:35:38 PM

Last enriched: 12/24/2025, 8:47:14 PM

Last updated: 2/7/2026, 2:17:02 PM

Views: 59

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats