{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-68218","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-12-16T13:41:40.256Z","datePublished":"2025-12-16T13:57:12.733Z","dateUpdated":"2026-08-05T12:10:17.092Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:10:17.092Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: fix lockdep WARN due to partition scan work\n\nBlktests test cases nvme/014, 057 and 058 fail occasionally due to a\nlockdep WARN. As reported in the Closes tag URL, the WARN indicates that\na deadlock can happen due to the dependency among disk->open_mutex,\nkblockd workqueue completion and partition_scan_work completion.\n\nTo avoid the lockdep WARN and the potential deadlock, cut the dependency\nby running the partition_scan_work not by kblockd workqueue but by\nnvme_wq."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - A malicious NVMe/TCP, RDMA, or FC controller can remotely drive namespace discovery, rapid remapping, ANA changes, and removal through protocol responses and asynchronous events.\nAC:L - The controller controls namespace presentation and removal and can repeatedly trigger rapid lifecycle changes to overlap automated partition scanning and device closure.\nPR:N - Once the host is connected, an NVMe-oF peer needs no privileges on the vulnerable host; authentication is optional and unauthenticated NVMe/TCP deployments are supported.\nUI:N - Namespace scanning and systemd-udevd device opening and closure occur automatically in a configured persistent NVMe-oF deployment.\nS:U - The deadlock affects resources within the host kernel's existing security authority and does not cross a virtualization or isolation boundary.\nC:N - The defect creates a circular locking dependency without exposing memory or providing an information-disclosure primitive.\nI:N - No memory corruption, unauthorized write, or control-flow modification results from the workqueue deadlock.\nA:H - The circular dependency can deadlock NVMe and block-layer work and device teardown, hanging storage operations and potentially critical system services."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/host/multipath.c"],"versions":[{"version":"60de2e03f984cfbcdc12fa552f95087c35a05a98","lessThan":"89456dab7ba5ab63d60945440926673a3205e829","status":"affected","versionType":"git"},{"version":"4a57f42e5ed42cb8f1beb262c4f6d3e698939e4e","lessThan":"e2a897ad5f538d314955c747a0a2edb184fcdecd","status":"affected","versionType":"git"},{"version":"1f021341eef41e77a633186e9be5223de2ce5d48","lessThan":"ef4ab2a8abe554379e10303ae86f7c501336ba0d","status":"affected","versionType":"git"},{"version":"1f021341eef41e77a633186e9be5223de2ce5d48","lessThan":"b03eb63288a8ffe3adfb34e68309c8e2edb06d0b","status":"affected","versionType":"git"},{"version":"1f021341eef41e77a633186e9be5223de2ce5d48","lessThan":"6d87cd5335784351280f82c47cc8a657271929c3","status":"affected","versionType":"git"},{"version":"a91b7eddf45afeeb9c5ece11dddff5de0921b00f","status":"affected","versionType":"git"},{"version":"6.1.118","lessThan":"6.1.159","status":"affected","versionType":"semver"},{"version":"6.6.62","lessThan":"6.6.118","status":"affected","versionType":"semver"},{"version":"6.11.9","lessThan":"6.12","status":"affected","versionType":"semver"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/host/multipath.c"],"versions":[{"version":"6.12","status":"affected"},{"version":"0","lessThan":"6.12","status":"unaffected","versionType":"semver"},{"version":"6.1.159","lessThanOrEqual":"6.1.*","status":"unaffected","versionType":"semver"},{"version":"6.6.118","lessThanOrEqual":"6.6.*","status":"unaffected","versionType":"semver"},{"version":"6.12.60","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.17.10","lessThanOrEqual":"6.17.*","status":"unaffected","versionType":"semver"},{"version":"6.18","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.1.118","versionEndExcluding":"6.1.159"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6.62","versionEndExcluding":"6.6.118"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.12","versionEndExcluding":"6.12.60"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.12","versionEndExcluding":"6.17.10"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.12","versionEndExcluding":"6.18"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11.9"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/89456dab7ba5ab63d60945440926673a3205e829"},{"url":"https://git.kernel.org/stable/c/e2a897ad5f538d314955c747a0a2edb184fcdecd"},{"url":"https://git.kernel.org/stable/c/ef4ab2a8abe554379e10303ae86f7c501336ba0d"},{"url":"https://git.kernel.org/stable/c/b03eb63288a8ffe3adfb34e68309c8e2edb06d0b"},{"url":"https://git.kernel.org/stable/c/6d87cd5335784351280f82c47cc8a657271929c3"}],"title":"nvme-multipath: fix lockdep WARN due to partition scan work","x_generator":{"engine":"bippy-1.2.0"}}}}