{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-38397 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-38397 is a medium-severity vulnerability in Linux kernel, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-38397 and fix it if it is affected.\n\nWhat it is: CVE-2025-38397 is a medium-severity vulnerability in Linux kernel, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-38397 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-38397/ (Markdown: https://insights.sbomify.com/CVE-2025-38397/index.md)","id":"CVE-2025-38397","markdown":"https://insights.sbomify.com/CVE-2025-38397/index.md","name":"CVE-2025-38397","record":{"aliases":["BELL-CVE-2025-38397","GHSA-cfvr-4cm5-x2r3","UBUNTU-CVE-2025-38397"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NVMe","requires_auth":"low_privilege","summary":"A suspicious RCU usage warning in the Linux kernel NVMe multipath driver can lead to system instability or crashes during NVMe over TCP operations.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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\nnvme-multipath: fix suspicious RCU usage warning\n\nWhen I run the NVME over TCP test in virtme-ng, I get the following\n\"suspicious RCU usage\" warning in nvme_mpath_add_sysfs_link():\n\n'''\n[    5.024557][   T44] nvmet: Created nvm controller 1 for subsystem nqn.2025-06.org.nvmexpress.mptcp for NQN nqn.2014-08.org.nvmexpress:uuid:f7f6b5e0-ff97-4894-98ac-c85309e0bc77.\n[    5.027401][  T183] nvme nvme0: creating 2 I/O queues.\n[    5.029017][  T183] nvme nvme0: mapped 2/0/0 default/read/poll queues.\n[    5.032587][  T183] nvme nvme0: new ctrl: NQN \"nqn.2025-06.org.nvmexpress.mptcp\", addr 127.0.0.1:4420, hostnqn: nqn.2014-08.org.nvmexpress:uuid:f7f6b5e0-ff97-4894-98ac-c85309e0bc77\n[    5.042214][   T25]\n[    5.042440][   T25] =============================\n[    5.042579][   T25] WARNING: suspicious RCU usage\n[    5.042705][   T25] 6.16.0-rc3+ #23 Not tainted\n[    5.042812][   T25] -----------------------------\n[    5.042934][   T25] drivers/nvme/host/multipath.c:1203 RCU-list traversed in non-reader section!!\n[    5.043111][   T25]\n[    5.043111][   T25] other info that might help us debug this:\n[    5.043111][   T25]\n[    5.043341][   T25]\n[    5.043341][   T25] rcu_scheduler_active = 2, debug_locks = 1\n[    5.043502][   T25] 3 locks held by kworker/u9:0/25:\n[    5.043615][   T25]  #0: ffff888008730948 ((wq_completion)async){+.+.}-{0:0}, at: process_one_work+0x7ed/0x1350\n[    5.043830][   T25]  #1: ffffc900001afd40 ((work_completion)(\u0026entry-\u003ework)){+.+.}-{0:0}, at: process_one_work+0xcf3/0x1350\n[    5.044084][   T25]  #2: ffff888013ee0020 (\u0026head-\u003esrcu){.+.+}-{0:0}, at: nvme_mpath_add_sysfs_link.part.0+0xb4/0x3a0\n[    5.044300][   T25]\n[    5.044300][   T25] stack backtrace:\n[    5.044439][   T25] CPU: 0 UID: 0 PID: 25 Comm: kworker/u9:0 Not tainted 6.16.0-rc3+ #23 PREEMPT(full)\n[    5.044441][   T25] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\n[    5.044442][   T25] Workqueue: async async_run_entry_fn\n[    5.044445][   T25] Call Trace:\n[    5.044446][   T25]  \u003cTASK\u003e\n[    5.044449][   T25]  dump_stack_lvl+0x6f/0xb0\n[    5.044453][   T25]  lockdep_rcu_suspicious.cold+0x4f/0xb1\n[    5.044457][   T25]  nvme_mpath_add_sysfs_link.part.0+0x2fb/0x3a0\n[    5.044459][   T25]  ? queue_work_on+0x90/0xf0\n[    5.044461][   T25]  ? lockdep_hardirqs_on+0x78/0x110\n[    5.044466][   T25]  nvme_mpath_set_live+0x1e9/0x4f0\n[    5.044470][   T25]  nvme_mpath_add_disk+0x240/0x2f0\n[    5.044472][   T25]  ? __pfx_nvme_mpath_add_disk+0x10/0x10\n[    5.044475][   T25]  ? add_disk_fwnode+0x361/0x580\n[    5.044480][   T25]  nvme_alloc_ns+0x81c/0x17c0\n[    5.044483][   T25]  ? kasan_quarantine_put+0x104/0x240\n[    5.044487][   T25]  ? __pfx_nvme_alloc_ns+0x10/0x10\n[    5.044495][   T25]  ? __pfx_nvme_find_get_ns+0x10/0x10\n[    5.044496][   T25]  ? rcu_read_lock_any_held+0x45/0xa0\n[    5.044498][   T25]  ? validate_chain+0x232/0x4f0\n[    5.044503][   T25]  nvme_scan_ns+0x4c8/0x810\n[    5.044506][   T25]  ? __pfx_nvme_scan_ns+0x10/0x10\n[    5.044508][   T25]  ? find_held_lock+0x2b/0x80\n[    5.044512][   T25]  ? ktime_get+0x16d/0x220\n[    5.044517][   T25]  ? kvm_clock_get_cycles+0x18/0x30\n[    5.044520][   T25]  ? __pfx_nvme_scan_ns_async+0x10/0x10\n[    5.044522][   T25]  async_run_entry_fn+0x97/0x560\n[    5.044523][   T25]  ? rcu_is_watching+0x12/0xc0\n[    5.044526][   T25]  process_one_work+0xd3c/0x1350\n[    5.044532][   T25]  ? __pfx_process_one_work+0x10/0x10\n[    5.044536][   T25]  ? assign_work+0x16c/0x240\n[    5.044539][   T25]  worker_thread+0x4da/0xd50\n[    5.044545][   T25]  ? __pfx_worker_thread+0x10/0x10\n[    5.044546][   T25]  kthread+0x356/0x5c0\n[    5.044548][   T25]  ? __pfx_kthread+0x10/0x10\n[    5.044549][   T25]  ? ret_from_fork+0x1b/0x2e0\n[    5.044552][   T25]  ? __lock_release.isra.0+0x5d/0x180\n[    5.044553][   T25]  ? ret_from_fork+0x1b/0x2e0\n[    5.044555][   T25]  ? rcu_is_watching+0x12/0xc0\n[    5.044557][   T25]  ? __pfx_kthread+0x10/0x10\n[    5.04\n---truncated---","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":"nvme-multipath: fix suspicious RCU usage warning","id":"CVE-2025-38397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"spi: spi-qpic-snand: reallocate BAM transactions","id":"CVE-2025-38398"},"packages":[],"prev":{"headline":"fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass","id":"CVE-2025-38396"},"products":["Linux"],"published":"2025-07-25","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A suspicious RCU usage warning in the Linux kernel NVMe multipath driver can lead to system instability or crashes during NVMe over TCP operations.","url":"https://insights.sbomify.com/CVE-2025-38397/"}