CVE-2025-48753Public exploit

Service interrupt via unguarded SpinLock unlock

Published May 24, 2025 · Updated May 24, 2025

Race condition in SpinLock in Obsidian Dynamics Anode 0.1.0 allows local users to cause a service interrupt through concurrent access. The safe public SpinLock::unlock method clears the atomic lock flag without requiring ownership of the active guard, so another thread can acquire the lock while the first still accesses protected data. Exploitation requires a consuming application to call unlock while a guard remains live; the published consequence is limited to application availability.

CVSS severity2.9
Low
EPSS probability0.24%
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 SpinLock in Obsidian Dynamics Anode 0.1.0 allows local users to cause a service interrupt through concurrent access. The safe public SpinLock::unlock method clears the atomic lock flag without requiring ownership of the active guard, so another thread can acquire the lock while the first still accesses protected data. Exploitation requires a consuming application to call unlock while a guard remains live; the published consequence is limited to application availability.

The record

CVE
CVE-2025-48753
Published
May 24, 2025
Updated
May 24, 2025
Vendor
Obsidian Dynamics
Product
Anode
Classifications
CWE-362, CAPEC-26, T1499
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?

Obsidian Dynamics · Anodeversion=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

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)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CAPEC-26Leveraging Race Conditions
T1499Endpoint Denial of Service

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