---
id: CVE-2025-23131
title: |-
  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
summary: |-
  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 und…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-476
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 2.6.31, < 6.14.2'
patched:
  - linux_kernel 6.14.2
published: '2025-04-16'
updated: '2026-07-04'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-23131'
references:
  - url: 'https://git.kernel.org/stable/c/10b7a59814765d18d43555c9cef4eb3048b7e8a3'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/7109d69bec6edce546dc870e66bd2b668a3d5549'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/8e2bad543eca5c25cd02cbc63d72557934d45f13'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a1c41aebb184d9228a440dcb6761224e65b0e49a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/b73c4ad4d387fe5bc988145bd9f1bc0de76afd5c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c7837e2c96559663c33f43da403d9cf3cf77cfa7'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ee28d99d789b077565cbe0377374d1e826c64d93'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00191
epssPercentile: 0.09082
ingestedAt: '2026-07-04T12:56:09.216Z'
---

## Overview

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.

## Affected

- `linux_kernel >= 2.6.31, < 6.14.2`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.14.2`