redoxOS Kernel setitimer denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.0$0-$5k0.00

Summaryinfo

A vulnerability was found in redoxOS Kernel. It has been rated as problematic. The impacted element is the function setitimer. Performing a manipulation results in denial of service. This vulnerability is identified as CVE-2025-46158. The attack is only possible with local access. Additionally, an exploit exists. It is recommended to apply a patch to fix this issue.

Detailsinfo

A vulnerability classified as problematic has been found in redoxOS Kernel (version unknown). This affects the function setitimer. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:

An issue in redoxOS kernel before commit 5d41cd7c allows a local attacker to cause a denial of service via the `setitimer` syscall

It is possible to read the advisory at gitlab.redox-os.org. This vulnerability is uniquely identified as CVE-2025-46158 since 04/22/2025. The exploitability is told to be easy. Attacking locally is a requirement. Technical details and a public exploit are known.

The exploit is shared for download at github.com. It is declared as proof-of-concept.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at gitlab.redox-os.org.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔒

Patch: gitlab.redox-os.org

Timelineinfo

04/22/2025 CVE reserved
06/20/2025 +59 days Advisory disclosed
06/20/2025 +0 days VulDB entry created
06/27/2025 +7 days VulDB entry last update

Sourcesinfo

Advisory: 164
Status: Confirmed

CVE: CVE-2025-46158 (🔒)
GCVE (CVE): GCVE-0-2025-46158
GCVE (VulDB): GCVE-100-313551
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 06/20/2025 21:21
Updated: 06/27/2025 04:02
Changes: 06/20/2025 21:21 (58), 06/27/2025 04:02 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!