CVE-2025-66646: CWE-476: NULL Pointer Dereference in RIOT-OS RIOT
RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. A vulnerability was discovered in the IPv6 fragmentation reassembly implementation of RIOT OS v2025.07. When receiving an fragmented IPv6 packet with fragment offset 0 and an empty payload, the payload pointer is set to NULL. However, the implementation still tries to copy the payload into the reassembly buffer, resulting in a NULL pointer dereference which crashes the OS (DoS). To trigger the vulnerability, the `gnrc_ipv6_ext_frag` module must be enabled and the attacker must be able to send arbitrary IPv6 packets to the victim. RIOT OS v2025.10 fixes the issue.
AI Analysis
Technical Summary
CVE-2025-66646 is a NULL pointer dereference vulnerability classified under CWE-476 found in the IPv6 fragmentation reassembly implementation of RIOT OS, an open-source operating system tailored for IoT and embedded devices. Specifically, when the system receives a fragmented IPv6 packet with a fragment offset of zero but an empty payload, the payload pointer is set to NULL. Despite this, the code attempts to copy the payload into the reassembly buffer, causing a NULL pointer dereference that crashes the OS, resulting in a denial of service. The vulnerability requires the gnrc_ipv6_ext_frag module to be enabled and an attacker capable of sending arbitrary IPv6 packets to the device. RIOT OS versions prior to 2025.10 are affected, with the vulnerability patched in version 2025.10. The CVSS 4.0 score is 1.7 (low severity), reflecting the limited impact and ease of exploitation without authentication or user interaction. No known exploits have been reported in the wild. This vulnerability primarily impacts availability by causing device crashes, which can disrupt IoT device operations and potentially affect larger systems relying on these devices.
Potential Impact
For European organizations, the primary impact of this vulnerability is a denial of service on IoT and embedded devices running vulnerable versions of RIOT OS. This can lead to temporary loss of device functionality, which may disrupt critical infrastructure, industrial automation, smart city applications, and other IoT-dependent services. Given the increasing reliance on IoT devices in sectors such as manufacturing, energy, healthcare, and transportation across Europe, exploitation could degrade operational continuity and safety. Although the vulnerability does not allow for data theft or system compromise beyond DoS, the interruption of services could have cascading effects, especially in environments where IoT devices are integral to monitoring and control. The low CVSS score indicates limited risk, but targeted attacks on critical IoT deployments could still cause meaningful disruption.
Mitigation Recommendations
The primary mitigation is to upgrade all RIOT OS deployments to version 2025.10 or later, where the vulnerability is fixed. Organizations should audit their IoT and embedded device inventories to identify devices running vulnerable RIOT OS versions. If upgrading is not immediately feasible, disabling the gnrc_ipv6_ext_frag module can prevent exploitation by removing the vulnerable IPv6 fragmentation reassembly functionality. Network-level controls should be implemented to restrict or filter incoming IPv6 traffic, especially from untrusted sources, to reduce exposure to crafted fragmented packets. Monitoring network traffic for unusual IPv6 fragmentation patterns can help detect attempted exploitation. Additionally, implementing segmentation and isolation of IoT devices limits the impact of any potential DoS. Regularly applying security updates and maintaining an asset management program for IoT devices is critical to prevent exploitation of such vulnerabilities.
Affected Countries
Germany, France, Netherlands, United Kingdom, Italy, Spain, Sweden
CVE-2025-66646: CWE-476: NULL Pointer Dereference in RIOT-OS RIOT
Description
RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. A vulnerability was discovered in the IPv6 fragmentation reassembly implementation of RIOT OS v2025.07. When receiving an fragmented IPv6 packet with fragment offset 0 and an empty payload, the payload pointer is set to NULL. However, the implementation still tries to copy the payload into the reassembly buffer, resulting in a NULL pointer dereference which crashes the OS (DoS). To trigger the vulnerability, the `gnrc_ipv6_ext_frag` module must be enabled and the attacker must be able to send arbitrary IPv6 packets to the victim. RIOT OS v2025.10 fixes the issue.
AI-Powered Analysis
Technical Analysis
CVE-2025-66646 is a NULL pointer dereference vulnerability classified under CWE-476 found in the IPv6 fragmentation reassembly implementation of RIOT OS, an open-source operating system tailored for IoT and embedded devices. Specifically, when the system receives a fragmented IPv6 packet with a fragment offset of zero but an empty payload, the payload pointer is set to NULL. Despite this, the code attempts to copy the payload into the reassembly buffer, causing a NULL pointer dereference that crashes the OS, resulting in a denial of service. The vulnerability requires the gnrc_ipv6_ext_frag module to be enabled and an attacker capable of sending arbitrary IPv6 packets to the device. RIOT OS versions prior to 2025.10 are affected, with the vulnerability patched in version 2025.10. The CVSS 4.0 score is 1.7 (low severity), reflecting the limited impact and ease of exploitation without authentication or user interaction. No known exploits have been reported in the wild. This vulnerability primarily impacts availability by causing device crashes, which can disrupt IoT device operations and potentially affect larger systems relying on these devices.
Potential Impact
For European organizations, the primary impact of this vulnerability is a denial of service on IoT and embedded devices running vulnerable versions of RIOT OS. This can lead to temporary loss of device functionality, which may disrupt critical infrastructure, industrial automation, smart city applications, and other IoT-dependent services. Given the increasing reliance on IoT devices in sectors such as manufacturing, energy, healthcare, and transportation across Europe, exploitation could degrade operational continuity and safety. Although the vulnerability does not allow for data theft or system compromise beyond DoS, the interruption of services could have cascading effects, especially in environments where IoT devices are integral to monitoring and control. The low CVSS score indicates limited risk, but targeted attacks on critical IoT deployments could still cause meaningful disruption.
Mitigation Recommendations
The primary mitigation is to upgrade all RIOT OS deployments to version 2025.10 or later, where the vulnerability is fixed. Organizations should audit their IoT and embedded device inventories to identify devices running vulnerable RIOT OS versions. If upgrading is not immediately feasible, disabling the gnrc_ipv6_ext_frag module can prevent exploitation by removing the vulnerable IPv6 fragmentation reassembly functionality. Network-level controls should be implemented to restrict or filter incoming IPv6 traffic, especially from untrusted sources, to reduce exposure to crafted fragmented packets. Monitoring network traffic for unusual IPv6 fragmentation patterns can help detect attempted exploitation. Additionally, implementing segmentation and isolation of IoT devices limits the impact of any potential DoS. Regularly applying security updates and maintaining an asset management program for IoT devices is critical to prevent exploitation of such vulnerabilities.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
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/17/2025, 7:50:57 PM
Last updated: 12/18/2025, 3:54:11 AM
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14856: Code Injection in y_project RuoYi
MediumCVE-2025-14841: NULL Pointer Dereference in OFFIS DCMTK
MediumCVE-2025-14837: Code Injection in ZZCMS
MediumCVE-2025-14836: Cleartext Storage in a File or on Disk in ZZCMS
MediumCVE-2025-14834: SQL Injection in code-projects Simple Stock System
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.