In the Linux kernel, the following vulnerability has been resolved: locking/spinlock/debug: Fix data-race in do_raw_write_lock KCSAN reports: BUG:… (CVE-2025-68336)
A data race vulnerability in the Linux kernel's locking/spinlock/debug code was identified and resolved. The issue involved inconsistent use of WRITE_ONCE() in the do_raw_write_lock function, leading to potential concurrency problems detected by Kernel Concurrency Sanitizer (KCSAN). The vulnerability does not impact confidentiality or integrity but can cause availability issues due to kernel crashes or instability. No known exploits are reported in the wild. No specific affected versions are provided in the data.
AI Analysis
Technical Summary
The vulnerability CVE-2025-68336 in the Linux kernel relates to a data race condition in the do_raw_write_lock function within the locking/spinlock/debug subsystem. KCSAN detected concurrent read and write accesses to the same memory location without proper synchronization, specifically in the debug_write_lock_before() part, which was not converted to use WRITE_ONCE() unlike debug_write_lock_after(). This inconsistency could lead to kernel crashes or instability (availability impact). The issue was addressed by ensuring consistent use of WRITE_ONCE() to prevent data races.
Potential Impact
The vulnerability does not affect confidentiality or integrity but has a high impact on availability due to the potential for kernel crashes or instability caused by the data race condition. There are no known exploits in the wild, reducing immediate risk, but the underlying concurrency bug could cause system reliability issues.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description references a commit that fixes the issue by applying WRITE_ONCE() consistently. Users should monitor official Linux kernel advisories and apply updates once available to address this data race condition.
In the Linux kernel, the following vulnerability has been resolved: locking/spinlock/debug: Fix data-race in do_raw_write_lock KCSAN reports: BUG:… (CVE-2025-68336)
Description
A data race vulnerability in the Linux kernel's locking/spinlock/debug code was identified and resolved. The issue involved inconsistent use of WRITE_ONCE() in the do_raw_write_lock function, leading to potential concurrency problems detected by Kernel Concurrency Sanitizer (KCSAN). The vulnerability does not impact confidentiality or integrity but can cause availability issues due to kernel crashes or instability. No known exploits are reported in the wild. No specific affected versions are provided in the data.
CVSS v3.1
Score 7.5high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2025-68336 in the Linux kernel relates to a data race condition in the do_raw_write_lock function within the locking/spinlock/debug subsystem. KCSAN detected concurrent read and write accesses to the same memory location without proper synchronization, specifically in the debug_write_lock_before() part, which was not converted to use WRITE_ONCE() unlike debug_write_lock_after(). This inconsistency could lead to kernel crashes or instability (availability impact). The issue was addressed by ensuring consistent use of WRITE_ONCE() to prevent data races.
Potential Impact
The vulnerability does not affect confidentiality or integrity but has a high impact on availability due to the potential for kernel crashes or instability caused by the data race condition. There are no known exploits in the wild, reducing immediate risk, but the underlying concurrency bug could cause system reliability issues.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description references a commit that fixes the issue by applying WRITE_ONCE() consistently. Users should monitor official Linux kernel advisories and apply updates once available to address this data race condition.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-hrvw-g8xf-vhvj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-68336"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d29c2644c7f84779a1
Added to database: 07/30/2026, 15:50:42 UTC
Last enriched: 07/30/2026, 18:55:24 UTC
Last updated: 09/10/2026, 19:26:53 UTC
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.