System crash via oversized device-mapper ioctl parameters
Published Jan 23, 2024 · Updated Nov 4, 2025
Denial of service in the Linux kernel through 6.7.1 allows local users to crash the system through a crafted device-mapper ioctl. copy_params in drivers/md/dm-ioctl.c forwards an unchecked param_kernel->data_size above INT_MAX to kvmalloc, triggering a kernel warning and crash. Access requires CAP_SYS_ADMIN in the initial namespace, effectively root privileges, and the demonstrated consequence is system availability loss only.
Summary
What happened
Denial of service in the Linux kernel through 6.7.1 allows local users to crash the system through a crafted device-mapper ioctl. copy_params in drivers/md/dm-ioctl.c forwards an unchecked param_kernel->data_size above INT_MAX to kvmalloc, triggering a kernel warning and crash. Access requires CAP_SYS_ADMIN in the initial namespace, effectively root privileges, and the demonstrated consequence is system availability loss only.
The record
- CVE
- CVE-2024-23851
- Published
- Jan 23, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- ctl_ioctl Syzkaller and C crash reproducersproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo