{"api_version":"1","generated_at":"2026-08-15T08:45:14+00:00","cve":"CVE-2026-74386","urls":{"html":"https://cve.report/CVE-2026-74386","api":"https://cve.report/api/cve/CVE-2026-74386.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74386","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74386"},"summary":{"title":"nvmet-tcp: fix page fragment cache leak in error path","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fix page fragment cache leak in error path\n\nIn nvmet_tcp_alloc_queue(), when a connection is closed during the\nallocation process (e.g., nvmet_tcp_set_queue_sock() returns -ENOTCONN),\nthe error handling jumps to out_destroy_sq and then to out_ida_remove\nwithout draining the page fragment cache.\n\nAlthough nvmet_tcp_free_cmd() is called in some error paths to release\nindividual page fragments, the underlying page cache reference held by\nqueue->pf_cache is never released. The first allocation using pf_cache\nis the call to nvmet_tcp_alloc_cmd() for queue->connect, which happens\nafter ida_alloc() returns successfully. This results in a page leak each\ntime a connection fails during allocation, which could lead to memory\nexhaustion over time if connections are repeatedly opened and closed.\n\nFix this by calling page_frag_cache_drain() before freeing the queue\nstructure in the out_ida_remove label.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:22:40","updated_at":"2026-08-15 06:22:40"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a43a9abc1ebf663f0aa56a729106f68dd9c77da6","name":"https://git.kernel.org/stable/c/a43a9abc1ebf663f0aa56a729106f68dd9c77da6","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5fbe83a374f09561a0f0c1f4aa021501ffd681eb","name":"https://git.kernel.org/stable/c/5fbe83a374f09561a0f0c1f4aa021501ffd681eb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ba3209704b3cd46961e4e081af5c52a780785648","name":"https://git.kernel.org/stable/c/ba3209704b3cd46961e4e081af5c52a780785648","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4dae393956093c807212918fd91a8fc70df15338","name":"https://git.kernel.org/stable/c/4dae393956093c807212918fd91a8fc70df15338","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74386","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74386","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 a43a9abc1ebf663f0aa56a729106f68dd9c77da6 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 ba3209704b3cd46961e4e081af5c52a780785648 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 5fbe83a374f09561a0f0c1f4aa021501ffd681eb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 4dae393956093c807212918fd91a8fc70df15338 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.0","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.0 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.97 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.40 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/nvme/target/tcp.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"a43a9abc1ebf663f0aa56a729106f68dd9c77da6","status":"affected","version":"872d26a391da92ed8f0c0f5cb5fef428067b7f30","versionType":"git"},{"lessThan":"ba3209704b3cd46961e4e081af5c52a780785648","status":"affected","version":"872d26a391da92ed8f0c0f5cb5fef428067b7f30","versionType":"git"},{"lessThan":"5fbe83a374f09561a0f0c1f4aa021501ffd681eb","status":"affected","version":"872d26a391da92ed8f0c0f5cb5fef428067b7f30","versionType":"git"},{"lessThan":"4dae393956093c807212918fd91a8fc70df15338","status":"affected","version":"872d26a391da92ed8f0c0f5cb5fef428067b7f30","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/nvme/target/tcp.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.0"},{"lessThan":"5.0","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.97","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.40","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.97","versionStartIncluding":"5.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.40","versionStartIncluding":"5.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"5.0","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"5.0","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fix page fragment cache leak in error path\n\nIn nvmet_tcp_alloc_queue(), when a connection is closed during the\nallocation process (e.g., nvmet_tcp_set_queue_sock() returns -ENOTCONN),\nthe error handling jumps to out_destroy_sq and then to out_ida_remove\nwithout draining the page fragment cache.\n\nAlthough nvmet_tcp_free_cmd() is called in some error paths to release\nindividual page fragments, the underlying page cache reference held by\nqueue->pf_cache is never released. The first allocation using pf_cache\nis the call to nvmet_tcp_alloc_cmd() for queue->connect, which happens\nafter ida_alloc() returns successfully. This results in a page leak each\ntime a connection fails during allocation, which could lead to memory\nexhaustion over time if connections are repeatedly opened and closed.\n\nFix this by calling page_frag_cache_drain() before freeing the queue\nstructure in the out_ida_remove label."}],"providerMetadata":{"dateUpdated":"2026-08-15T05:59:01.786Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/a43a9abc1ebf663f0aa56a729106f68dd9c77da6"},{"url":"https://git.kernel.org/stable/c/ba3209704b3cd46961e4e081af5c52a780785648"},{"url":"https://git.kernel.org/stable/c/5fbe83a374f09561a0f0c1f4aa021501ffd681eb"},{"url":"https://git.kernel.org/stable/c/4dae393956093c807212918fd91a8fc70df15338"}],"title":"nvmet-tcp: fix page fragment cache leak in error path","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74386","datePublished":"2026-08-15T05:59:01.786Z","dateReserved":"2026-08-15T05:44:03.890Z","dateUpdated":"2026-08-15T05:59:01.786Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:22:40","lastModifiedDate":"2026-08-15 06:22:40","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74386","Ordinal":"1","Title":"nvmet-tcp: fix page fragment cache leak in error path","CVE":"CVE-2026-74386","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74386","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fix page fragment cache leak in error path\n\nIn nvmet_tcp_alloc_queue(), when a connection is closed during the\nallocation process (e.g., nvmet_tcp_set_queue_sock() returns -ENOTCONN),\nthe error handling jumps to out_destroy_sq and then to out_ida_remove\nwithout draining the page fragment cache.\n\nAlthough nvmet_tcp_free_cmd() is called in some error paths to release\nindividual page fragments, the underlying page cache reference held by\nqueue->pf_cache is never released. The first allocation using pf_cache\nis the call to nvmet_tcp_alloc_cmd() for queue->connect, which happens\nafter ida_alloc() returns successfully. This results in a page leak each\ntime a connection fails during allocation, which could lead to memory\nexhaustion over time if connections are repeatedly opened and closed.\n\nFix this by calling page_frag_cache_drain() before freeing the queue\nstructure in the out_ida_remove label.","Type":"Description","Title":"nvmet-tcp: fix page fragment cache leak in error path"}]}}}