{
  "id": "CVE-2026-74401",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-74401",
  "published_at": "2026-08-15T05:59:12.099Z",
  "title": "dlm: fix add msg handle in send_queue ordered",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 9.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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-\u003eseq is not ordered\naccording the oldest seq number. This ordering is required by\ndlm_receive_ack as \"before(mh-\u003eseq, seq)\" will stop to check for older\nsequence numbers that are ordered in the tail of \"node-\u003esend_queue\".\n\nThe side effects of not having it correct ordered regarding\n\"before(mh-\u003eseq, 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.",
  "cvss_by_source": {
    "cna": 9.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 489d8e559c6596eb08e16447d9830bc39afbe54e, \u003c 482606fea302d8bab86901d7426c3716980d99a8",
          "\u003e= 489d8e559c6596eb08e16447d9830bc39afbe54e, \u003c ae9e534e502a0f48c12baf83608c5de0ff0eab11",
          "\u003e= 489d8e559c6596eb08e16447d9830bc39afbe54e, \u003c 6369619f1b665f12d8c99cc6ff733c64eb08b22e",
          "\u003e= 489d8e559c6596eb08e16447d9830bc39afbe54e, \u003c 712714f818d83373847874ab0f8e426be79296cf",
          "\u003e= 489d8e559c6596eb08e16447d9830bc39afbe54e, \u003c 4d45250b1d22960f86d83245be188b16e456218b",
          "\u003e= 489d8e559c6596eb08e16447d9830bc39afbe54e, \u003c d2248cb70c070f8f04762872772e155b59016f17"
        ],
        "fixed_in": [
          "482606fea302d8bab86901d7426c3716980d99a8",
          "ae9e534e502a0f48c12baf83608c5de0ff0eab11",
          "6369619f1b665f12d8c99cc6ff733c64eb08b22e",
          "712714f818d83373847874ab0f8e426be79296cf",
          "4d45250b1d22960f86d83245be188b16e456218b",
          "d2248cb70c070f8f04762872772e155b59016f17"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "5.14"
        ],
        "fixed_in": [
          "0",
          "6.1.191",
          "6.6.145",
          "6.12.97",
          "6.18.40",
          "7.1.5",
          "7.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 482606fea302d8bab86901d7426c3716980d99a8 or ae9e534e502a0f48c12baf83608c5de0ff0eab11 or 6369619f1b665f12d8c99cc6ff733c64eb08b22e or 712714f818d83373847874ab0f8e426be79296cf or 4d45250b1d22960f86d83245be188b16e456218b or d2248cb70c070f8f04762872772e155b59016f17 or later.",
      "Upgrade Linux to 0 or 6.1.191 or 6.6.145 or 6.12.97 or 6.18.40 or 7.1.5 or 7.2 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
