{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-38405","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-04-16T04:51:24.012Z","datePublished":"2025-07-25T13:12:07.926Z","dateUpdated":"2026-08-05T12:01:38.515Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T12:01:38.515Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet: fix memory leak of bio integrity\n\nIf nvmet receives commands with metadata there is a continuous memory\nleak of kmalloc-128 slab or more precisely bio->bi_integrity.\n\nSince commit bf4c89fc8797 (\"block: don't call bio_uninit from bio_endio\")\neach user of bio_init has to use bio_uninit as well. Otherwise the bio\nintegrity is not getting free. Nvmet uses bio_init for inline bios.\n\nUninit the inline bio to complete deallocation of integrity in bio."}],"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 - The leak is driven entirely by NVMe commands received by the nvmet target from a remote host, and the affected metadata/PI path is only reachable via nvmet-rdma (the sole transport setting NVMF_METADATA_SUPPORTED), which runs over routable RoCEv2/iWARP fabrics. No local access to the target is needed.\nAC:L - Every read/write command carrying protection information leaks a bip allocation with 100% reliability — no race, no memory-layout dependency, and the attacker fully controls the I/O size that selects the vulnerable inline-bio path. Repetition to exhaust memory is unconstrained.\nPR:N - NVMe-oF requires no authentication by default; the target admits hosts based on a client-supplied, trivially spoofable host NQN or with allow_any_host enabled, so an unauthenticated remote peer can establish a queue and issue I/O.\nUI:N - The leak occurs purely from processing attacker-sent NVMe I/O commands; no action by any local user or administrator is required once the target is serving.\nS:U - The leaked kernel slab memory and its consequences are confined to the kernel of the target host; no security boundary such as a hypervisor or IOMMU domain is crossed.\nC:N - The orphaned bio_integrity_payload is never re-read or exposed, and no out-of-bounds or uninitialized data is returned to the attacker, so there is no information disclosure.\nI:N - bio_init() resets bi_integrity to NULL on reuse, so the leak causes no use-after-free, double-free, or any other memory corruption — no kernel data is modified.\nA:H - The leak is unbounded and driven at line-rate I/O speed by the remote attacker, so sustained traffic exhausts kernel slab memory leading to OOM kills, allocation failures and system hang/panic on the storage target."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/nvme/target/nvmet.h"],"versions":[{"version":"bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f","lessThan":"431e58d56fcb5ff1f9eb630724a922e0d2a941df","status":"affected","versionType":"git"},{"version":"bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f","lessThan":"2e2028fcf924d1c6df017033c8d6e28b735a0508","status":"affected","versionType":"git"},{"version":"bf4c89fc8797f5c0964a0c3d561fbe7e8483b62f","lessThan":"190f4c2c863af7cc5bb354b70e0805f06419c038","status":"affected","versionType":"git"},{"version":"64149da0fddbbfe43e11c0348d8c8b4171dae3a2","status":"affected","versionType":"git"},{"version":"6.10.10","lessThan":"6.11","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/target/nvmet.h"],"versions":[{"version":"6.11","status":"affected"},{"version":"0","lessThan":"6.11","status":"unaffected","versionType":"semver"},{"version":"6.12.37","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.15.6","lessThanOrEqual":"6.15.*","status":"unaffected","versionType":"semver"},{"version":"6.16","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.11","versionEndExcluding":"6.12.37"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.15.6"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.11","versionEndExcluding":"6.16"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.10.10"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/431e58d56fcb5ff1f9eb630724a922e0d2a941df"},{"url":"https://git.kernel.org/stable/c/2e2028fcf924d1c6df017033c8d6e28b735a0508"},{"url":"https://git.kernel.org/stable/c/190f4c2c863af7cc5bb354b70e0805f06419c038"}],"title":"nvmet: fix memory leak of bio integrity","x_generator":{"engine":"bippy-1.2.0"}}}}