CVE-2026-74401

CVE CVE-2026-74401EUVD EUVD-2026-59548Published 2026-08-15T05:59:12.000ZLast changed 2026-08-17T05:46:44.000ZCVSS 9.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 5.14; 489d8e559c6596eb08e16447d9830bc39afbe54e <4d45250b1d22960f86d83245be188b16e456218b; 489d8e559c6596eb08e16447d9830bc39afbe54e <6369619f1b665f12d8c99cc6ff733c64eb08b22e; patch: 7.2; 489d8e559c6596eb08e16447d9830bc39afbe54e <d2248cb70c070f8f04762872772e155b59016f17; patch: 6.18.40; patch: 6.6.145; 489d8e559c6596eb08e16447d9830bc39afbe54e <712714f818d83373847874ab0f8e426be79296cf; patch: 6.12.97; 489d8e559c6596eb08e16447d9830bc39afbe54e <ae9e534e502a0f48c12baf83608c5de0ff0eab11; patch: 7.1.5; patch: 0

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.