Answer in brief
CVE-2025-68336 records a High severity (CVSS 7.5) vulnerability in locking/spinlock/debug: Fix data-race in do_raw_write_lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1a365e822372ba24c9da0822bc583894f6f3d821 <8e5b2cf10844402054b52b489b525dc30cc16908 || >=1a365e822372ba24c9da0822bc583894f6f3d821 <c228cb699a07a5f2d596d186bc5c314c99bb8bbf || >=1a365e822372ba24c9da0822bc583894f6f3d821 <93bd23524d63deb80fb85beb2e43fafeb1043d0f || >=1a365e822372ba24c9da0822bc583894f6f3d821 <39d2ef113416f1a4205b03fb0aa2e428d1412c77 || >=1a365e822372ba24c9da0822bc583894f6f3d821 <b163a5e8c703201c905d6ec7920ed79d167e8442 || >=1a365e822372ba24c9da0822bc583894f6f3d821 <16b3590c0e1e615757dade098c8fbc0d4f040c76 || >=1a365e822372ba24c9da0822bc583894f6f3d821 <396a9270a7b90886be501611b13aa636f2e8c703 || >=1a365e822372ba24c9da0822bc583894f6f3d821 <c14ecb555c3ee80eeb030a4e46d00e679537f03a || 3106fb78d3579c8e9c9b3040f7f7841981919624 || c0911024ff927ba5c4786b507004cb615be1d776 || 09226e5c38639437565af01e6009a9286a351d04 || c7673f01604fa722b9d7c1e29e17cec1b8ae09c5 || c120c3dbeb76305235c8e557f84d9e2d7d0f5933 || >=4.4.209 <4.5 || >=4.9.209 <4.10 || >=4.14.164 <4.15 || >=4.19.95 <4.20 || >=5.4.11 <5.5 | 8e5b2cf10844402054b52b489b525dc30cc16908, c228cb699a07a5f2d596d186bc5c314c99bb8bbf, 93bd23524d63deb80fb85beb2e43fafeb1043d0f, 39d2ef113416f1a4205b03fb0aa2e428d1412c77, b163a5e8c703201c905d6ec7920ed79d167e8442, 16b3590c0e1e615757dade098c8fbc0d4f040c76, 396a9270a7b90886be501611b13aa636f2e8c703, c14ecb555c3ee80eeb030a4e46d00e679537f03a, 4.5, 4.10, 4.15, 4.20, 5.5 |
| Linux/Linuxgeneric | 5.5 | Not reported |
Published upstream
Dec 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.