VulnerabilityPublished 22 Dec 2025Updated 30 Jul 2026

CVE-2025-68336: Linux kernel · locking/spinlock/debug: Fix data-race in do_raw_write_lock

Source GCVE Database

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-hrvw-g8xf-vhvj

What to do

AI-suggested

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.

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.

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.

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.

References

Community reviews

Loading reviews…