{"api_version":"1","generated_at":"2026-09-12T11:10:19+00:00","cve":"CVE-2026-89494","urls":{"html":"https://cve.report/CVE-2026-89494","api":"https://cve.report/api/cve/CVE-2026-89494.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89494","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89494"},"summary":{"title":"ocfs2: validate lengths in dlm_mig_lockres_handler","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: validate lengths in dlm_mig_lockres_handler\n\nA node receiving a DLM_MIG_LOCKRES message trusts several fields of the\npeer-supplied dlm_migratable_lockres without validation.  num_locks and\nlockname_len are bounded only on the sending side, and the message is\nnever checked to actually carry num_locks migratable_lock entries.  As a\nresult dlm_process_recovery_data() walks mres->ml[0..num_locks) past the\nkmalloc(data_len) copy of the message (an out-of-bounds read that ends in\na BUG_ON panic), and dlm_init_lockres() copies lockname_len bytes into the\nfixed 32-byte o2dlm_lockname slab object (a heap out-of-bounds write). \nBoth are reachable by any node in the domain.\n\nValidate these fields right after dlm_grab(), before anything uses them --\nincluding the not-joined error path, which already prints mres->lockname\nwith the unbounded lockname_len as a %.*s precision.  Reject the message\nunless lockname_len <= DLM_LOCKID_NAME_MAX, num_locks <=\nDLM_MAX_MIGRATABLE_LOCKS (the bound the sender already asserts), and the\npayload is large enough to hold the claimed locks.  Conforming recovery\nand migration messages are unaffected.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:19:31","updated_at":"2026-09-11 20:19:31"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/50c4cc9183e11f83427efbf770f54851f4471c02","name":"https://git.kernel.org/stable/c/50c4cc9183e11f83427efbf770f54851f4471c02","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b54e03d9b3697d25f4a0063cf717d459c5e3ad94","name":"https://git.kernel.org/stable/c/b54e03d9b3697d25f4a0063cf717d459c5e3ad94","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a8facb1670b4a0612183198e758d9539ef628ed9","name":"https://git.kernel.org/stable/c/a8facb1670b4a0612183198e758d9539ef628ed9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f33041906885f96e190cde54e61ddc69de39e3ee","name":"https://git.kernel.org/stable/c/f33041906885f96e190cde54e61ddc69de39e3ee","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89494","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89494","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6714d8e86bf443f6f7af50f9d432025649f091f5 f33041906885f96e190cde54e61ddc69de39e3ee git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6714d8e86bf443f6f7af50f9d432025649f091f5 50c4cc9183e11f83427efbf770f54851f4471c02 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6714d8e86bf443f6f7af50f9d432025649f091f5 a8facb1670b4a0612183198e758d9539ef628ed9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6714d8e86bf443f6f7af50f9d432025649f091f5 b54e03d9b3697d25f4a0063cf717d459c5e3ad94 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.16","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.16 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.109 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-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/ocfs2/dlm/dlmrecovery.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"f33041906885f96e190cde54e61ddc69de39e3ee","status":"affected","version":"6714d8e86bf443f6f7af50f9d432025649f091f5","versionType":"git"},{"lessThan":"50c4cc9183e11f83427efbf770f54851f4471c02","status":"affected","version":"6714d8e86bf443f6f7af50f9d432025649f091f5","versionType":"git"},{"lessThan":"a8facb1670b4a0612183198e758d9539ef628ed9","status":"affected","version":"6714d8e86bf443f6f7af50f9d432025649f091f5","versionType":"git"},{"lessThan":"b54e03d9b3697d25f4a0063cf717d459c5e3ad94","status":"affected","version":"6714d8e86bf443f6f7af50f9d432025649f091f5","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/ocfs2/dlm/dlmrecovery.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.16"},{"lessThan":"2.6.16","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.109","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.109","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"2.6.16","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"2.6.16","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: validate lengths in dlm_mig_lockres_handler\n\nA node receiving a DLM_MIG_LOCKRES message trusts several fields of the\npeer-supplied dlm_migratable_lockres without validation.  num_locks and\nlockname_len are bounded only on the sending side, and the message is\nnever checked to actually carry num_locks migratable_lock entries.  As a\nresult dlm_process_recovery_data() walks mres->ml[0..num_locks) past the\nkmalloc(data_len) copy of the message (an out-of-bounds read that ends in\na BUG_ON panic), and dlm_init_lockres() copies lockname_len bytes into the\nfixed 32-byte o2dlm_lockname slab object (a heap out-of-bounds write). \nBoth are reachable by any node in the domain.\n\nValidate these fields right after dlm_grab(), before anything uses them --\nincluding the not-joined error path, which already prints mres->lockname\nwith the unbounded lockname_len as a %.*s precision.  Reject the message\nunless lockname_len <= DLM_LOCKID_NAME_MAX, num_locks <=\nDLM_MAX_MIGRATABLE_LOCKS (the bound the sender already asserts), and the\npayload is large enough to hold the claimed locks.  Conforming recovery\nand migration messages are unaffected."}],"providerMetadata":{"dateUpdated":"2026-09-11T19:43:45.455Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/f33041906885f96e190cde54e61ddc69de39e3ee"},{"url":"https://git.kernel.org/stable/c/50c4cc9183e11f83427efbf770f54851f4471c02"},{"url":"https://git.kernel.org/stable/c/a8facb1670b4a0612183198e758d9539ef628ed9"},{"url":"https://git.kernel.org/stable/c/b54e03d9b3697d25f4a0063cf717d459c5e3ad94"}],"title":"ocfs2: validate lengths in dlm_mig_lockres_handler","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89494","datePublished":"2026-09-11T19:43:45.455Z","dateReserved":"2026-09-11T19:38:34.714Z","dateUpdated":"2026-09-11T19:43:45.455Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:19:31","lastModifiedDate":"2026-09-11 20:19:31","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89494","Ordinal":"1","Title":"ocfs2: validate lengths in dlm_mig_lockres_handler","CVE":"CVE-2026-89494","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89494","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: validate lengths in dlm_mig_lockres_handler\n\nA node receiving a DLM_MIG_LOCKRES message trusts several fields of the\npeer-supplied dlm_migratable_lockres without validation.  num_locks and\nlockname_len are bounded only on the sending side, and the message is\nnever checked to actually carry num_locks migratable_lock entries.  As a\nresult dlm_process_recovery_data() walks mres->ml[0..num_locks) past the\nkmalloc(data_len) copy of the message (an out-of-bounds read that ends in\na BUG_ON panic), and dlm_init_lockres() copies lockname_len bytes into the\nfixed 32-byte o2dlm_lockname slab object (a heap out-of-bounds write). \nBoth are reachable by any node in the domain.\n\nValidate these fields right after dlm_grab(), before anything uses them --\nincluding the not-joined error path, which already prints mres->lockname\nwith the unbounded lockname_len as a %.*s precision.  Reject the message\nunless lockname_len <= DLM_LOCKID_NAME_MAX, num_locks <=\nDLM_MAX_MIGRATABLE_LOCKS (the bound the sender already asserts), and the\npayload is large enough to hold the claimed locks.  Conforming recovery\nand migration messages are unaffected.","Type":"Description","Title":"ocfs2: validate lengths in dlm_mig_lockres_handler"}]}}}