dlm: prevent NPD when writing a positive value to event_done
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8511a2728ab82cab398e39d019f5cf1246021c1c · < b73c4ad4d387fe5bc988145bd9f1bc0de76afd5c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dlm: prevent NPD when writing a positive value to event_done
do_uevent returns the value written to event_done. In case it is a positive value, new_lockspace would undo all the work, and lockspace would not be set. __dlm_new_lockspace, however, would treat that positive value as a success due to commit 8511a2728ab8 ("dlm: fix use count with multiple joins").
Down the line, device_create_lockspace would pass that NULL lockspace to dlm_find_lockspace_local, leading to a NULL pointer dereference.
Treating such positive values as successes prevents the problem. Given this has been broken for so long, this is unlikely to break userspace expectations.
From the CVE record · Linux
The Linux kernel’s dlm code can dereference a NULL lockspace pointer when a positive value is written to event_done during lockspace creation. A local actor able to write that value could trigger the dereference; the input does not specify authentication requirements or further impact.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.