{"api_version":"1","generated_at":"2026-08-15T08:44:36+00:00","cve":"CVE-2026-74401","urls":{"html":"https://cve.report/CVE-2026-74401","api":"https://cve.report/api/cve/CVE-2026-74401.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74401","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74401"},"summary":{"title":"dlm: fix add msg handle in send_queue ordered","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndlm: fix add msg handle in send_queue ordered\n\nIn a benchmark scenario triggering a lot of requests that triggers a lot\nof DLM messages on the network it can be that the mh->seq is not ordered\naccording the oldest seq number. This ordering is required by\ndlm_receive_ack as \"before(mh->seq, seq)\" will stop to check for older\nsequence numbers that are ordered in the tail of \"node->send_queue\".\n\nThe side effects of not having it correct ordered regarding\n\"before(mh->seq, seq)\" are refcounting issues and use-after free.\n\nI only was able to reproduce this issue in a experimental DLM branch\nand a user space DLM benchmark that uses io_uring. After changing this I\ndon't experienced any refcounting with the sending buffer issues anymore.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:22:42","updated_at":"2026-08-15 06:22:42"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/d2248cb70c070f8f04762872772e155b59016f17","name":"https://git.kernel.org/stable/c/d2248cb70c070f8f04762872772e155b59016f17","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/6369619f1b665f12d8c99cc6ff733c64eb08b22e","name":"https://git.kernel.org/stable/c/6369619f1b665f12d8c99cc6ff733c64eb08b22e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ae9e534e502a0f48c12baf83608c5de0ff0eab11","name":"https://git.kernel.org/stable/c/ae9e534e502a0f48c12baf83608c5de0ff0eab11","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/712714f818d83373847874ab0f8e426be79296cf","name":"https://git.kernel.org/stable/c/712714f818d83373847874ab0f8e426be79296cf","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4d45250b1d22960f86d83245be188b16e456218b","name":"https://git.kernel.org/stable/c/4d45250b1d22960f86d83245be188b16e456218b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74401","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74401","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 489d8e559c6596eb08e16447d9830bc39afbe54e ae9e534e502a0f48c12baf83608c5de0ff0eab11 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 489d8e559c6596eb08e16447d9830bc39afbe54e 6369619f1b665f12d8c99cc6ff733c64eb08b22e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 489d8e559c6596eb08e16447d9830bc39afbe54e 712714f818d83373847874ab0f8e426be79296cf git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 489d8e559c6596eb08e16447d9830bc39afbe54e 4d45250b1d22960f86d83245be188b16e456218b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 489d8e559c6596eb08e16447d9830bc39afbe54e d2248cb70c070f8f04762872772e155b59016f17 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.145 6.6.* 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":["fs/dlm/midcomms.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ae9e534e502a0f48c12baf83608c5de0ff0eab11","status":"affected","version":"489d8e559c6596eb08e16447d9830bc39afbe54e","versionType":"git"},{"lessThan":"6369619f1b665f12d8c99cc6ff733c64eb08b22e","status":"affected","version":"489d8e559c6596eb08e16447d9830bc39afbe54e","versionType":"git"},{"lessThan":"712714f818d83373847874ab0f8e426be79296cf","status":"affected","version":"489d8e559c6596eb08e16447d9830bc39afbe54e","versionType":"git"},{"lessThan":"4d45250b1d22960f86d83245be188b16e456218b","status":"affected","version":"489d8e559c6596eb08e16447d9830bc39afbe54e","versionType":"git"},{"lessThan":"d2248cb70c070f8f04762872772e155b59016f17","status":"affected","version":"489d8e559c6596eb08e16447d9830bc39afbe54e","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/dlm/midcomms.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.14"},{"lessThan":"5.14","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.145","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.6.145","versionStartIncluding":"5.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.97","versionStartIncluding":"5.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.40","versionStartIncluding":"5.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"5.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"5.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndlm: fix add msg handle in send_queue ordered\n\nIn a benchmark scenario triggering a lot of requests that triggers a lot\nof DLM messages on the network it can be that the mh->seq is not ordered\naccording the oldest seq number. This ordering is required by\ndlm_receive_ack as \"before(mh->seq, seq)\" will stop to check for older\nsequence numbers that are ordered in the tail of \"node->send_queue\".\n\nThe side effects of not having it correct ordered regarding\n\"before(mh->seq, seq)\" are refcounting issues and use-after free.\n\nI only was able to reproduce this issue in a experimental DLM branch\nand a user space DLM benchmark that uses io_uring. After changing this I\ndon't experienced any refcounting with the sending buffer issues anymore."}],"providerMetadata":{"dateUpdated":"2026-08-15T05:59:12.099Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ae9e534e502a0f48c12baf83608c5de0ff0eab11"},{"url":"https://git.kernel.org/stable/c/6369619f1b665f12d8c99cc6ff733c64eb08b22e"},{"url":"https://git.kernel.org/stable/c/712714f818d83373847874ab0f8e426be79296cf"},{"url":"https://git.kernel.org/stable/c/4d45250b1d22960f86d83245be188b16e456218b"},{"url":"https://git.kernel.org/stable/c/d2248cb70c070f8f04762872772e155b59016f17"}],"title":"dlm: fix add msg handle in send_queue ordered","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74401","datePublished":"2026-08-15T05:59:12.099Z","dateReserved":"2026-08-15T05:44:03.892Z","dateUpdated":"2026-08-15T05:59:12.099Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:22:42","lastModifiedDate":"2026-08-15 06:22:42","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74401","Ordinal":"1","Title":"dlm: fix add msg handle in send_queue ordered","CVE":"CVE-2026-74401","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74401","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndlm: fix add msg handle in send_queue ordered\n\nIn a benchmark scenario triggering a lot of requests that triggers a lot\nof DLM messages on the network it can be that the mh->seq is not ordered\naccording the oldest seq number. This ordering is required by\ndlm_receive_ack as \"before(mh->seq, seq)\" will stop to check for older\nsequence numbers that are ordered in the tail of \"node->send_queue\".\n\nThe side effects of not having it correct ordered regarding\n\"before(mh->seq, seq)\" are refcounting issues and use-after free.\n\nI only was able to reproduce this issue in a experimental DLM branch\nand a user space DLM benchmark that uses io_uring. After changing this I\ndon't experienced any refcounting with the sending buffer issues anymore.","Type":"Description","Title":"dlm: fix add msg handle in send_queue ordered"}]}}}