What is CVE-2026-74401?

CVE-2026-74401 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10, affecting Linux kernel versions from 5.14 onward and patched in 6.6.145, 6.12.97, 6.18.40 and others. CVE-2026-74401 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-74401?

CVE-2026-74401 has a CVSS score of 9.8 out of 10, rated Critical severity. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-74401?

Yes, CVE-2026-74401 has been patched. Fixed versions include 6.6.145, 6.12.97, 6.18.40 and others. If you are running Linux kernel 5.14 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-74401 actively exploited?

CVE-2026-74401 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-74401

Critical

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.

Package Linux Kernel

Published 2026-08-15

Last modified 2026-08-17

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

9.8

out of 10

Critical

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 5.14 and later are affected. Fixed in 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2 and their respective stable series.

Affected from

≥ 5.14

Fixed in

✓ 6.6.145 6.6.x ✓ 6.12.97 6.12.x ✓ 6.18.40 6.18.x ✓ 7.1.5 7.1.x ✓ 7.2

References

5 total

Details

CVE ID CVE-2026-74401

Severity Critical

CVSS score 9.8 / 10

CVSS version 3.1

Published 2026-08-15

Modified 2026-08-17

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-74401?

CVE-2026-74401 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.8 out of 10 . It affects Linux kernel versions from 5.14 onward and has been patched in 6.6.145, 6.12.97, 6.18.40 and others. CVE-2026-74401 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-74401?

CVE-2026-74401 has a CVSS score of 9.8 out of 10, rated Critical severity (CVSS 3.1). The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-74401?

Yes. CVE-2026-74401 has been patched. Fixed versions include 6.6.145, 6.12.97, 6.18.40 and others. If you are running Linux kernel 5.14 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-74401 actively exploited?

No. CVE-2026-74401 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.