CVE-2025-40134

dm: fix NULL pointer dereference in __dm_suspend()

State
Published
Severity
Not scored
Published
Nov 12, 2025
Updated
May 11, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

dm: fix NULL pointer dereference in __dm_suspend()

There is a race condition between dm device suspend and table load that can lead to null pointer dereference. The issue occurs when suspend is invoked before table load completes:

BUG: kernel NULL pointer dereference, address: 0000000000000054 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 6 PID: 6798 Comm: dmsetup Not tainted 6.6.0-g7e52f5f0ca9b #62 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 RIP: 0010:blk_mq_wait_quiesce_done+0x0/0x50 Call Trace: <TASK> blk_mq_quiesce_queue+0x2c/0x50 dm_stop_queue+0xd/0x20 __dm_suspend+0x130/0x330 dm_suspend+0x11a/0x180 dev_suspend+0x27e/0x560 ctl_ioctl+0x4cf/0x850 dm_ctl_ioctl+0xd/0x20 vfs_ioctl+0x1d/0x50 __se_sys_ioctl+0x9b/0xc0 __x64_sys_ioctl+0x19/0x30 x64_sys_call+0x2c4a/0x4620 do_syscall_64+0x9e/0x1b0

The issue can be triggered as below:

T1 T2 dm_suspend table_load __dm_suspend dm_setup_md_queue dm_mq_init_request_queue blk_mq_init_allocated_queue => q->mq_ops = set->ops; (1) dm_stop_queue / dm_wait_for_completion => q->tag_set NULL pointer! (2) => q->tag_set = set; (3)

Fix this by checking if a valid table (map) exists before performing request-based suspend and waiting for target I/O. When map is NULL, skip these table-dependent suspend steps.

Even when map is NULL, no I/O can reach any target because there is no table loaded; I/O submitted in this state will fail early in the DM layer. Skipping the table-dependent suspend logic in this case is safe and avoids NULL pointer dereferences.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • c4576aed8d85d808cd6443bda58393d525207d01 to before 9dc43ea6a20ff83fe9a5fe4be47ae0fbf2409b98Affected
  • c4576aed8d85d808cd6443bda58393d525207d01 to before 30f95b7eda5966b81cb221bd569c0f095a068cf6Affected
  • c4576aed8d85d808cd6443bda58393d525207d01 to before a0e54bd8d7ea79127fe9920df3ae36f85e79ac7cAffected
  • c4576aed8d85d808cd6443bda58393d525207d01 to before a802901b75e13cc306f1b7ab0f062135c8034e9eAffected
  • c4576aed8d85d808cd6443bda58393d525207d01 to before 846cafc4725ca727d94f9c4b5f789c1a7c8fb6feAffected
  • c4576aed8d85d808cd6443bda58393d525207d01 to before 19ca4528666990be376ac3eb6fe667b03db5324dAffected
  • c4576aed8d85d808cd6443bda58393d525207d01 to before 331c2dd8ca8bad1a3ac10cce847ffb76158eece4Affected
  • c4576aed8d85d808cd6443bda58393d525207d01 to before 8d33a030c566e1f105cd5bf27f37940b6367f3beAffected
LinuxLinux
  • 5.0Affected
  • before 5.0Not affected
  • 5.4.301 through 5.4.*Not affected
  • 5.10.246 through 5.10.*Not affected
  • 5.15.195 through 5.15.*Not affected
  • 6.1.156 through 6.1.*Not affected
  • 6.6.112 through 6.6.*Not affected
  • 6.12.53 through 6.12.*Not affected
  • 6.17.3 through 6.17.*Not affected
  • 6.18 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.