CVE-2026-74401

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH 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 — 5 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%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
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.

Data Freshness Timeline

(refreshed 49× in last 7d / 49× 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.

  1. 2026-08-21 09:24 UTCGHSA enrichment
  2. 2026-08-21 05:31 UTCGHSA enrichment
  3. 2026-08-21 01:39 UTCEG score recompute
  4. 2026-08-21 01:39 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 21:47 UTCGHSA enrichment
  7. 2026-08-20 17:55 UTCGHSA enrichment
  8. 2026-08-20 14:02 UTCGHSA enrichment
  9. 2026-08-20 09:54 UTCGHSA enrichment
  10. 2026-08-20 06:02 UTCGHSA enrichment
  11. 2026-08-20 02:09 UTCGHSA enrichment
  12. 2026-08-19 22:15 UTCGHSA enrichment
  13. 2026-08-19 18:22 UTCEG score recompute
  14. 2026-08-19 18:22 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 14:22 UTCGHSA enrichment
  17. 2026-08-19 10:28 UTCGHSA enrichment
  18. 2026-08-19 06:36 UTCGHSA enrichment
  19. 2026-08-19 02:42 UTCGHSA enrichment
  20. 2026-08-18 22:46 UTCGHSA enrichment
  21. 2026-08-18 18:49 UTCGHSA enrichment
  22. 2026-08-18 14:57 UTCEG score recompute
  23. 2026-08-18 14:57 UTCGHSA enrichment
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-18 13:49 UTCEPSS rescore
Show 24 more
  1. 2026-08-18 10:26 UTCGHSA enrichment
  2. 2026-08-18 06:33 UTCGHSA enrichment
  3. 2026-08-18 02:40 UTCGHSA enrichment
  4. 2026-08-17 22:48 UTCGHSA enrichment
  5. 2026-08-17 18:55 UTCGHSA enrichment
  6. 2026-08-17 14:10 UTCEG score recompute
  7. 2026-08-17 14:10 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 10:18 UTCEG score recompute
  10. 2026-08-17 10:18 UTCGHSA enrichment
  11. 2026-08-17 06:26 UTCEG score recompute
  12. 2026-08-17 06:26 UTCGHSA enrichment
  13. 2026-08-17 05:55 UTCEG score recompute▲ 9.80
  14. 2026-08-17 05:55 UTCGHSA enrichment
  15. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  16. 2026-08-17 05:26 UTCEG score recompute
  17. 2026-08-17 05:26 UTCGHSA enrichment
  18. 2026-08-17 05:24 UTCMITRE cvelistV5
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:15 UTCEPSS rescore
  22. 2026-08-15 06:23 UTCNVD update
  23. 2026-08-15 06:14 UTCEG score recompute
  24. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 62.4% of all scored CVEs.
What is the CVSS score of CVE-2026-74401?
CVE-2026-74401 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74401?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74401, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs