CVE-2025-40134
Last modified
CVE-2025-40134 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= c4576aed8d85d808cd6443bda58393d525207d01, < 9dc43ea6a20ff83fe9a5fe4be47ae0fbf2409b98; >= c4576aed8d85d808cd6443bda58393d525207d01, < 30f95b7eda5966b81cb221bd569c0f095a068cf6; >= c4576aed8d85d808cd6443bda58393d525207d01, < a0e54bd8d7ea79127fe9920df3ae36f85e79ac7c; >= c4576aed8d85d808cd6443bda58393d525207d01, < a802901b75e13cc306f1b7ab0f062135c8034e9e; >= c4576aed8d85d808cd6443bda58393d525207d01, < 846cafc4725ca727d94f9c4b5f789c1a7c8fb6fe; >= c4576aed8d85d808cd6443bda58393d525207d01, < 19ca4528666990be376ac3eb6fe667b03db5324d; >= c4576aed8d85d808cd6443bda58393d525207d01, < 331c2dd8ca8bad1a3ac10cce847ffb76158eece4; >= c4576aed8d85d808cd6443bda58393d525207d01, < 8d33a030c566e1f105cd5bf27f37940b6367f3be |
| Linux | Linux | 5.0 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-40134?
How severe is CVE-2025-40134?
How do I fix CVE-2025-40134?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-40129In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2025-4013A vulnerability was found in PHPGurukul Art Gallery Manageme…9.8
- CVE-2025-40130In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40131In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40132In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40133In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2025-40135In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2025-40136In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40137In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40138In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40139In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-4014A vulnerability was found in PHPGurukul Art Gallery Manageme…9.8
Are you affected by CVE-2025-40134?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
