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.
Metrics
Affected Vendors & Products
References
History
Fri, 25 Apr 2025 03:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-476 |
Thu, 17 Apr 2025 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Wed, 16 Apr 2025 14:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
Title | dlm: prevent NPD when writing a positive value to event_done | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-04-16T14:13:13.056Z
Updated: 2025-05-26T05:19:08.896Z
Reserved: 2025-01-11T14:28:41.511Z
Link: CVE-2025-23131

No data.

Status : Awaiting Analysis
Published: 2025-04-16T15:16:07.547
Modified: 2025-04-17T20:22:16.240
Link: CVE-2025-23131
