CVE-2026-74401

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
49th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Oct 5, 2026
Patch available.
generic

dlm: fix add msg handle in send_queue ordered - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2248cb70c070f8f04762872772e155b59016f17
generic

dlm: fix add msg handle in send_queue ordered - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ae9e534e502a0f48c12baf83608c5de0ff0eab11
generic

dlm: fix add msg handle in send_queue ordered - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/712714f818d83373847874ab0f8e426be79296cf
generic

dlm: fix add msg handle in send_queue ordered - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6369619f1b665f12d8c99cc6ff733c64eb08b22e
generic

dlm: fix add msg handle in send_queue ordered - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d45250b1d22960f86d83245be188b16e456218b

Vendor Advisories for CVE-2026-74401(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-34.34) @ resolute2026-10-05ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1014.14) @ resolute2026-10-05ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1012.12~24.04.1) @ noble2026-10-05ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1007.8) @ resolute2026-10-05ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 56× in last 7d / 257× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 420 total refreshes for this CVE.

  1. 2026-10-05 06:46 UTCVendor advisory
  2. 2026-10-05 06:46 UTCGHSA enrichment
  3. 2026-10-05 02:23 UTCEG score recompute
  4. 2026-10-05 02:23 UTCVendor advisory
  5. 2026-10-05 02:23 UTCGHSA enrichment
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 21:57 UTCVendor advisory
  8. 2026-10-04 21:57 UTCGHSA enrichment
  9. 2026-10-04 16:27 UTCVendor advisory
  10. 2026-10-04 16:27 UTCGHSA enrichment
  11. 2026-10-04 12:03 UTCVendor advisory
  12. 2026-10-04 12:02 UTCGHSA enrichment
  13. 2026-10-04 07:19 UTCVendor advisory
  14. 2026-10-04 07:19 UTCGHSA enrichment
  15. 2026-10-04 03:27 UTCVendor advisory
  16. 2026-10-04 03:27 UTCGHSA enrichment
  17. 2026-10-03 19:31 UTCEG score recompute
  18. 2026-10-03 19:31 UTCVendor advisory
  19. 2026-10-03 19:31 UTCGHSA enrichment
  20. 2026-10-03 14:26 UTCEPSS rescore
  21. 2026-10-03 00:47 UTCVendor advisory
  22. 2026-10-03 00:47 UTCGHSA enrichment
  23. 2026-10-02 19:44 UTCEG score recompute
  24. 2026-10-02 19:44 UTCVendor advisory
  25. 2026-10-02 19:44 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 15:52 UTCVendor advisory
  2. 2026-10-02 15:51 UTCGHSA enrichment
  3. 2026-10-02 07:03 UTCVendor advisory
  4. 2026-10-02 07:03 UTCGHSA enrichment
  5. 2026-10-02 02:01 UTCEG score recompute
  6. 2026-10-02 02:01 UTCVendor advisory
  7. 2026-10-02 02:01 UTCGHSA enrichment
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 13:40 UTCVendor advisory
  10. 2026-10-01 13:40 UTCGHSA enrichment
  11. 2026-10-01 09:47 UTCVendor advisory
  12. 2026-10-01 09:47 UTCGHSA enrichment
  13. 2026-10-01 05:51 UTCVendor advisory
  14. 2026-10-01 05:51 UTCGHSA enrichment
  15. 2026-10-01 01:33 UTCVendor advisory
  16. 2026-10-01 01:33 UTCGHSA enrichment
  17. 2026-09-30 20:59 UTCEG score recompute
  18. 2026-09-30 20:59 UTCVendor advisory
  19. 2026-09-30 20:58 UTCGHSA enrichment
  20. 2026-09-29 15:24 UTCEPSS rescore
  21. 2026-09-29 07:44 UTCVendor advisory
  22. 2026-09-29 07:44 UTCGHSA enrichment
  23. 2026-09-29 03:52 UTCVendor advisory
  24. 2026-09-29 03:52 UTCGHSA enrichment
  25. 2026-09-28 23:59 UTCEG score recompute
  26. 2026-09-28 23:59 UTCVendor advisory
  27. 2026-09-28 23:59 UTCGHSA enrichment
  28. 2026-09-28 14:22 UTCEG score recompute
  29. 2026-09-28 14:22 UTCVendor advisory
  30. 2026-09-28 14:22 UTCGHSA enrichment
  31. 2026-09-28 13:52 UTCEPSS rescore
  32. 2026-09-28 10:29 UTCVendor advisory
  33. 2026-09-28 10:29 UTCGHSA enrichment
  34. 2026-09-28 06:36 UTCVendor advisory
  35. 2026-09-28 06:36 UTCGHSA enrichment
  36. 2026-09-28 02:44 UTCVendor advisory
  37. 2026-09-28 02:43 UTCGHSA enrichment
  38. 2026-09-27 22:44 UTCVendor advisory
  39. 2026-09-27 22:44 UTCGHSA enrichment
  40. 2026-09-27 16:43 UTCEG score recompute
  41. 2026-09-27 16:43 UTCVendor advisory
  42. 2026-09-27 16:43 UTCGHSA enrichment
  43. 2026-09-27 13:48 UTCEPSS rescore
  44. 2026-09-27 12:28 UTCVendor advisory
  45. 2026-09-27 12:28 UTCGHSA enrichment
  46. 2026-09-27 08:27 UTCEG score recompute
  47. 2026-09-27 08:27 UTCVendor advisory
  48. 2026-09-27 08:27 UTCGHSA enrichment
  49. 2026-09-26 15:59 UTCEPSS rescore
  50. 2026-09-26 00:28 UTCEPSS rescore
  51. 2026-09-25 10:16 UTCVendor advisory
  52. 2026-09-25 10:16 UTCGHSA enrichment
  53. 2026-09-25 06:23 UTCVendor advisory
  54. 2026-09-25 06:23 UTCGHSA enrichment
  55. 2026-09-25 02:31 UTCVendor advisory
  56. 2026-09-25 02:31 UTCGHSA enrichment
  57. 2026-09-24 16:26 UTCEG score recompute
  58. 2026-09-24 16:26 UTCVendor advisory
  59. 2026-09-24 16:26 UTCGHSA enrichment
  60. 2026-09-24 14:04 UTCEPSS rescore
  61. 2026-09-24 12:03 UTCVendor advisory
  62. 2026-09-24 12:03 UTCGHSA enrichment
  63. 2026-09-24 08:10 UTCVendor advisory
  64. 2026-09-24 08:10 UTCGHSA enrichment
  65. 2026-09-24 04:18 UTCVendor advisory
  66. 2026-09-24 04:18 UTCGHSA enrichment
  67. 2026-09-24 00:25 UTCVendor advisory
  68. 2026-09-24 00:25 UTCGHSA enrichment
  69. 2026-09-23 20:32 UTCEG score recompute
  70. 2026-09-23 20:32 UTCVendor advisory
  71. 2026-09-23 20:32 UTCGHSA enrichment
  72. 2026-09-23 17:54 UTCEPSS rescore
  73. 2026-09-23 16:28 UTCVendor advisory
  74. 2026-09-23 16:28 UTCGHSA enrichment
  75. 2026-09-23 12:26 UTCVendor advisory

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74401?
CVE-2026-74401 is a critical vulnerability published on August 15, 2026. 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…
When was CVE-2026-74401 disclosed?
CVE-2026-74401 was first published on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74401 actively exploited?
CVE-2026-74401 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74401?
CVE-2026-74401 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74401?
A fix for CVE-2026-74401 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74401 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74401

Explore →

Is Your Infrastructure Affected by CVE-2026-74401?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs