Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74401dlm: fix add msg handle in send_queue ordered

Description

In the Linux kernel, the following vulnerability has been resolved: dlm: fix add msg handle in send_queue ordered In a benchmark scenario triggering a lot of requests that triggers a lot of DLM messages on the network it can be that the mh->seq is not ordered according the oldest seq number. This ordering is required by dlm_receive_ack as "before(mh->seq, seq)" will stop to check for older sequence numbers that are ordered in the tail of "node->send_queue". The side effects of not having it correct ordered regarding "before(mh->seq, seq)" are refcounting issues and use-after free. I only was able to reproduce this issue in a experimental DLM branch and a user space DLM benchmark that uses io_uring. After changing this I don't experienced any refcounting with the sending buffer issues anymore.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74401, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.70% · top 46% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 489d8e559c6596eb08e16447d9830bc39afbe54e – < 482606fea302d8bab86901d7426c3716980d99a8
    • affected 489d8e559c6596eb08e16447d9830bc39afbe54e – < ae9e534e502a0f48c12baf83608c5de0ff0eab11
    • affected 489d8e559c6596eb08e16447d9830bc39afbe54e – < 6369619f1b665f12d8c99cc6ff733c64eb08b22e
    • affected 489d8e559c6596eb08e16447d9830bc39afbe54e – < 712714f818d83373847874ab0f8e426be79296cf
    • affected 489d8e559c6596eb08e16447d9830bc39afbe54e – < 4d45250b1d22960f86d83245be188b16e456218b
    • affected 489d8e559c6596eb08e16447d9830bc39afbe54e – < d2248cb70c070f8f04762872772e155b59016f17
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74401 badge
[![CVE-2026-74401](https://cveledger.app/badge/CVE-2026-74401.svg)](https://cveledger.app/cve/CVE-2026-74401)

Record last updated .