CVE-2025-48751Public exploit

Availability loss via safe premature unlock

Published May 24, 2025 · Updated May 24, 2025

Race condition in the tickbh ProcessLock 0.1.0 Rust crate allows local users to cause availability loss via an unexpected unlock call. The safe ProcessLock::unlock method can release a lock while a live LockGuard still represents it as held, allowing concurrent access to the protected region. Exploitation requires local code to invoke unlock at the wrong time; the published proof demonstrates overlapping access but documents neither data corruption nor code execution.

CVSS severity2.9
Low
EPSS probability0.27%
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

Race condition in the tickbh ProcessLock 0.1.0 Rust crate allows local users to cause availability loss via an unexpected unlock call. The safe ProcessLock::unlock method can release a lock while a live LockGuard still represents it as held, allowing concurrent access to the protected region. Exploitation requires local code to invoke unlock at the wrong time; the published proof demonstrates overlapping access but documents neither data corruption nor code execution.

The record

CVE
CVE-2025-48751
Published
May 24, 2025
Updated
May 24, 2025
Vendor
tickbh
Product
ProcessLock
Classifications
CWE-362
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 24, 2025CVE publishedPublication date reported by the CVE source.
  2. May 24, 2025Record 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.1.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

tickbh · ProcessLockversion=0.1.0

Published CVSS scores

2.9MITRECVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
9.8NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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