CVE-2024-53980Public exploit

Device hang via unmasked packet length bit

Published Nov 29, 2024 · Updated Dec 2, 2024

Infinite loop in RIOT 2024.07 and earlier allows physically proximate attackers to hang CC2538 devices via crafted IEEE 802.15.4 packets. The CC2538 receive path uses all eight length-byte bits to locate the CRC, although the radio masks bit 7, so a spoofed high bit reads beyond the RX FIFO and can falsely validate a bad frame. With AUTO_ACK enabled, the resulting CRC disagreement leaves TXACKDONE unset and the CPU spinning until the device is rebooted; transmitting the overlength field requires a software-defined radio.

CVSS severity6.9
Medium
EPSS probability0.76%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Infinite loop in RIOT 2024.07 and earlier allows physically proximate attackers to hang CC2538 devices via crafted IEEE 802.15.4 packets. The CC2538 receive path uses all eight length-byte bits to locate the CRC, although the radio masks bit 7, so a spoofed high bit reads beyond the RX FIFO and can falsely validate a bad frame. With AUTO_ACK enabled, the resulting CRC disagreement leaves TXACKDONE unset and the CPU spinning until the device is rebooted; transmitting the overlength field requires a software-defined radio.

The record

CVE
CVE-2024-53980
Published
Nov 29, 2024
Updated
Dec 2, 2024
Vendor
RIOT-OS
Product
RIOT
Classifications
CWE-835, T1499.004
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 29, 2024CVE publishedPublication date reported by the CVE source.
  2. Dec 2, 2024Record 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.

  1. Affected versionversion=0 <=2024.07
  2. Affected versionversion=<= 2024.07

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

RIOT-OS · RIOTversion=0 <=2024.07; version=<= 2024.07

Published CVSS scores

6.9GitHub, Inc.CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
7.5NIST National Vulnerability DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
6.5GitHub Security AdvisoryCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-835Loop with Unreachable Exit Condition ('Infinite Loop')
T1499.004Application or System Exploitation

Public exploit references

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