CVE-2026-46294 Details
Description
In the Linux kernel, the following vulnerability has been resolved: dm: fix a buffer overflow in ioctl processing Tony Asleson (using Claude) found a buffer overflow in dm-ioctl in the function retrieve_status: 1. The code in retrieve_status checks that the output string fits into the output buffer and writes the output string there 2. Then, the code aligns the "outptr" variable to the next 8-byte boundary: outptr = align_ptr(outptr); 3. The alignment doesn't check overflow, so outptr could point past the buffer end 4. The "for" loop is iterated again, it executes: remaining = len - (outptr - outbuf); 5. If "outptr" points past "outbuf + len", the arithmetics wraps around and the variable "remaining" contains unusually high number 6. With "remaining" being high, the code writes more data past the end of the buffer Luckily, this bug has no security implications because: 1. Only root can issue device mapper ioctls 2. The commonly used libraries that communicate with device mapper (libdevmapper and devicemapper-rs) use buffer size that is aligned to 8 bytes - thus, "outptr = align_ptr(outptr)" can't overshoot the input buffer and the bug can't happen accidentally
A buffer overflow vulnerability has been identified in the Linux kernel's device mapper (DM) IOCTL processing, specifically within the 'retrieve_status' function of the DM IOCTL driver. This vulnerability arises because the function aligns a pointer to the output buffer without properly checking for overflow, potentially allowing data to be written past the end of the buffer. Although this issue has been addressed in the Linux kernel, it is important to note that it does not pose a security risk, as only root users can issue device mapper IOCTL commands. Furthermore, commonly used libraries that interact with the device mapper, such as 'libdevmapper' and 'devicemapper-rs', utilize buffer sizes that are already aligned to 8 bytes, preventing the overflow from occurring in practice.
The vulnerability has been fixed in the Linux kernel. Users can upgrade to the latest version of the stable Linux kernel to address this issue.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2fa49cc884f6496a915c35621ba4da35649bf159 | kernel.org | Patch |
| https://git.kernel.org/stable/c/448ee8fb79c26a26599ffa4b2adeb4322d3d3d8c | kernel.org | Patch |
| https://git.kernel.org/stable/c/526ff9126a0ae087b65726e1faf31114c718020d | kernel.org | Patch |
| https://git.kernel.org/stable/c/5af6a879e915ae7bcd83695c316ebb32e1c61bc2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8daa6c708ef524089ae43f2aed9190acb26d7df8 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c8c5311237448f6ffeecc9aec2362e3692623668 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d271631023cbe1cbe7c31a0275ab797883be6e0a | kernel.org | Patch |
| https://git.kernel.org/stable/c/f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 2.6.12.1, < 5.10.258 >= 5.11, < 5.15.209 >= 5.16, < 6.1.175 >= 6.2, < 6.6.140 >= 6.7, < 6.12.88 >= 6.13, < 6.18.30 >= 6.19, < 7.0.7 2.6.12 - 2.6.12 rc2 2.6.12 rc3 2.6.12 rc4 2.6.12 rc5 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 23, 2026 | CVE Translated | [email protected] |
| Jul 8, 2026 | Initial Analysis | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 8, 2026 | New CVE Received | kernel.org |