dlm: fix add msg handle in send_queue ordered
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 489d8e559c6596eb08e16447d9830bc39afbe54e · < d2248cb70c070f8f04762872772e155b59016f17| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s DLM send queue can order message handles incorrectly under a high volume of network DLM messages. This can cause refcounting errors and a use-after-free. The report does not establish an attacker path or state whether authentication or user interaction is required.
Engineers running Linux kernels that use DLM should check their systems; affected versions are not specified.