cve.bz

CVE-2025-68336 linux linux

7.5 highEPSS 0.5%Fix available

High (7.5) in linux linux. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.248
  • Linux Linux: fixed in 5.15.198
  • Linux Linux: fixed in 6.1.160
  • Linux Linux: fixed in 6.6.120
  • Linux Linux: fixed in 6.12.62
  • Linux Linux: fixed in 6.17.12
  • Linux Linux: fixed in 6.18.1
  • Linux Linux: fixed in 6.19
  • Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-68336 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68336?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68336?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68336 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-68336

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-68336](https://cve.bz/cve/badge/CVE-2025-68336.svg)](https://cve.bz/cve/CVE-2025-68336)

HTML:

<a href="https://cve.bz/cve/CVE-2025-68336"><img src="https://cve.bz/cve/badge/CVE-2025-68336.svg" alt="CVE-2025-68336"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 4.4.209 before 4.5
Linuxfrom 4.9.209 before 4.10
Linuxfrom 4.14.164 before 4.15
Linuxfrom 4.19.95 before 4.20
Linuxfrom 5.4.11 before 5.5
Linux5.5 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.248
Linux5.155.15.198
Linux6.16.1.160
Linux6.66.6.120
Linux6.126.12.62
Linux6.176.17.12
Linux6.186.18.1
Linuxlater releases6.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux5.10.249-1DLA-4475-1
Debian11linux-6.16.1.162-1~deb11u1DLA-4476-1
Debian12linux6.1.162-1DEBIAN-CVE-2025-68336 DSA-6127-1
Debian13linux6.12.63-1DEBIAN-CVE-2025-68336
Debian14linux6.17.12-1DEBIAN-CVE-2025-68336
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68336
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68336
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68336
Ubuntu22.04:LTSlinux, linux-lowlatency5.15.0-173.183UBUNTU-CVE-2025-68336 USN-8096-1
Ubuntu22.04:LTSlinux-aws5.15.0-1103.110UBUNTU-CVE-2025-68336 USN-8096-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-68336 USN-8179-1
Ubuntu22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-68336 USN-8163-2
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2025-68336 USN-8440-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-68336
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-68336
Ubuntu22.04:LTSlinux-gcp5.15.0-1103.112UBUNTU-CVE-2025-68336 USN-8096-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2025-68336 USN-8179-4
79 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source6.18.5-1.1openSUSE-SU-2026:10039-1
openSUSETumbleweedkernel-source-longterm6.18.16-1.1openSUSE-SU-2026:10301-1
Azure Linux3kernel6.6.121.1-1AZL-72889
Alpaquita23linux-lts6.1.161-r0BELL-CVE-2025-68336
Alpaquita25linux-lts6.12.65-r0BELL-CVE-2025-68336
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-68336

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A data race was found in the Linux kernel's spinlock debugging code. A previous fix for data races in do_raw_write_lock() was incomplete: only the debug_write_lock_after() portion was converted to WRITE_ONCE(), leaving a racy access in the debug_write_lock_before() portion that the Kernel Concurrency Sanitizer (KCSAN) reports when concurrent tasks acquire a write lock. The race is confined to lock-debugging instrumentation and has no network attack vector; it requires local access to the running kernel, so Red Hat rates this flaw LOW impact (availability only; Red Hat CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). This is lower than the upstream CVE record's score of 7.5, whose network attack vector does not reflect the local, debug-only nature of the defect. The kernel and kernel-rt packages in Red Hat Enterprise Linux 8 (8.4 and later minor streams), Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, and Red Hat In-Vehicle OS 1 are affected; Red Hat Enterprise Linux 6, 7, and 8.2 are not affected because the vulnerable code is not present in those streams. For the affected streams the fix is deferred because the race affects debug bookkeeping rather than the correctness of the lock itself; the residual risk of running without the fix is limited to potentially incorrect spinlock debug diagnostics on systems using kernels built with these debugging options.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68336.

References

Check your stackJSON