dlm: fix add msg handle in send_queue ordered
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.145, 6.12.97, 6.18.40, 7.1.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 489d8e559c6596eb08e16447d9830bc39afbe54e · fixed in ae9e534e502a0f48c12baf83608c5de0ff0eab11; From 489d8e559c6596eb08e16447d9830bc39afbe54e · fixed in 6369619f1b665f12d8c99cc6ff733c64eb08b22e; From 489d8e559c6596eb08e16447d9830bc39afbe54e · fixed in 712714f818d83373847874ab0f8e426be79296cf; From 489d8e559c6596eb08e16447d9830bc39afbe54e · fixed in 4d45250b1d22960f86d83245be188b16e456218b; From 489d8e559c6596eb08e16447d9830bc39afbe54e · fixed in d2248cb70c070f8f04762872772e155b59016f17
- Linux Linux
5.14
- KernelLinux
From 5.14.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5