Cyber Resilience

CVE-2025-2838

DoS in Silabs Gecko Os 1.0.46

Published
26 March 2025
Modified
08 August 2025
CVSS Score v3 6.5
Click a component to see what it means
Raw vectorCVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0025 16th percentile
Risk Priority 49 floored blend · peak EPSS

Summary

CVE-2025-2838 is a medium-severity Infinite Loop (CWE-835) vulnerability in Silabs Gecko Os. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Silicon Labs Gecko OS DNS Response Processing Infinite Loop Denial-of-Service Vulnerability. This vulnerability allows network-adjacent attackers to create a denial-of-service condition on affected installations of Silicon Labs Gecko OS. Authentication is not required to exploit this vulnerability. The specific flaw…

more

exists within the processing of DNS responses. The issue results from a logic error that can lead to an infinite loop. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-23392.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-23937Same product: Silabs Gecko Os
CVE-2024-23938Same product: Silabs Gecko Os
CVE-2024-24731Same product: Silabs Gecko Os
CVE-2025-2837Same product: Silabs Gecko Os
CVE-2024-23973Same product: Silabs Gecko Os
CVE-2026-47145Same vendor: Silabs
CVE-2024-0240Same vendor: Silabs
CVE-2023-5310Same vendor: Silabs
CVE-2026-47146Same vendor: Silabs
CVE-2023-6640Same vendor: Silabs

Affected Assets

silabs
gecko os
1.0.46

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.

Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.

Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (reviews, testing, static analysis) directly prevent introduction of infinite-loop defects.

ID.RA-01 partial match
prevents

Static analysis and vuln scanning during asset assessment can detect unreachable loop exits.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can uncover infinite-loop conditions before release.

prevents

Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.

prevents

Application security requirements can specify loop-termination rules, indirectly reducing the weakness.

prevents

Secure coding standards directly address loop termination and prevent infinite loops.

none

Secure architecture principles encourage designs that avoid unreachable exit conditions.

none

Change management can require review of loop logic when code is modified.

References