{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68336 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68336 is a high-severity vulnerability in Linux, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68336 and fix it if it is affected.\n\nWhat it is: CVE-2025-68336 is a high-severity vulnerability in Linux, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68336 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68336/ (Markdown: https://insights.sbomify.com/CVE-2025-68336/index.md)","id":"CVE-2025-68336","markdown":"https://insights.sbomify.com/CVE-2025-68336/index.md","name":"CVE-2025-68336","record":{"aliases":["AZL-72889","BELL-CVE-2025-68336","DEBIAN-CVE-2025-68336","GHSA-hrvw-g8xf-vhvj","ROOT-OS-DEBIAN-11-CVE-2025-68336","ROOT-OS-DEBIAN-12-CVE-2025-68336","ROOT-OS-UBUNTU-2204-CVE-2025-68336","ROOT-OS-UBUNTU-2404-CVE-2025-68336","UBUNTU-CVE-2025-68336"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A data race in the Linux kernel's spinlock debug code can lead to inconsistent state, potentially causing system instability or crashes.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nlocking/spinlock/debug: Fix data-race in do_raw_write_lock\n\nKCSAN reports:\n\nBUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock\n\nwrite (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1:\n do_raw_write_lock+0x120/0x204\n _raw_write_lock_irq\n do_exit\n call_usermodehelper_exec_async\n ret_from_fork\n\nread to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0:\n do_raw_write_lock+0x88/0x204\n _raw_write_lock_irq\n do_exit\n call_usermodehelper_exec_async\n ret_from_fork\n\nvalue changed: 0xffffffff -\u003e 0x00000001\n\nReported by Kernel Concurrency Sanitizer on:\nCPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111\n\nCommit 1a365e822372 (\"locking/spinlock/debug: Fix various data races\") has\nadressed most of these races, but seems to be not consistent/not complete.\n\n\u003eFrom do_raw_write_lock() only debug_write_lock_after() part has been\nconverted to WRITE_ONCE(), but not debug_write_lock_before() part.\nDo it now.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"locking/spinlock/debug: Fix data-race in do_raw_write_lock","id":"CVE-2025-68336","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted","id":"CVE-2025-68337"},"packages":[],"prev":{"headline":"comedi: pcl818: fix null-ptr-deref in pcl818_ai_cancel()","id":"CVE-2025-68335"},"products":["Linux"],"published":"2025-12-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A data race in the Linux kernel's spinlock debug code can lead to inconsistent state, potentially causing system instability or crashes.","url":"https://insights.sbomify.com/CVE-2025-68336/"}