relibc pthread_rwlockattr_setpshared 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.2$0-$5k1.21

Summaryinfo

A vulnerability classified as problematic has been found in relibc. Affected is the function pthread_rwlockattr_setpshared. This manipulation causes denial of service. This vulnerability is registered as CVE-2026-38637. Furthermore, an exploit is available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in relibc (version now known). It has been declared as problematic. Affected by this vulnerability is the function pthread_rwlockattr_setpshared. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:

An issue in the pthread_rwlockattr_setpshared() function of relibc commit 61f42d allows attackers to cause a Denial of Service (DoS) via a crafted input.

The advisory is shared at gitlab.redox-os.org. This vulnerability is known as CVE-2026-38637 since 04/06/2026. Technical details and also a public exploit are known.

It is possible to download the exploit 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.2

VulDB Base Score: 3.5
VulDB Temp Score: 3.2
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: No
Local: No
Remote: Partially

Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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/06/2026 CVE reserved
06/25/2026 +80 days VulDB entry created
06/26/2026 +0 days Advisory disclosed
06/26/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: 264
Status: Confirmed

CVE: CVE-2026-38637 (🔒)
GCVE (CVE): GCVE-0-2026-38637
GCVE (VulDB): GCVE-100-374065
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 06/26/2026 01:24
Changes: 06/26/2026 01:24 (57)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!