CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's Distributed Lock Manager (DLM) component, where improper ordering of message handles in the send queue can lead to reference counting issues and potential use-after-free conditions. This flaw may be exploited in high-load scenarios, particularly when using user space DLM benchmarks with io_uring, resulting in instability or crashes. Organizations utilizing Linux systems with DLM in high-throughput environments should prioritize addressing this issue to mitigate risks associated with memory management errors.
Original NVD Description
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.