CVE-2026-46294: Linux kernel · dm: fix a buffer overflow in ioctl processing
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a, d271631023cbe1cbe7c31a0275ab797883be6e0a, c8c5311237448f6ffeecc9aec2362e3692623668 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 8 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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
References
- git.kernel.org/stable/c/c8c5311237448f6ffeecc9aec2362e3692623668 (opens in a new tab)
- git.kernel.org/stable/c/448ee8fb79c26a26599ffa4b2adeb4322d3d3d8c (opens in a new tab)
- git.kernel.org/stable/c/526ff9126a0ae087b65726e1faf31114c718020d (opens in a new tab)
- git.kernel.org/stable/c/f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a (opens in a new tab)
- git.kernel.org/stable/c/d271631023cbe1cbe7c31a0275ab797883be6e0a (opens in a new tab)
- git.kernel.org/stable/c/5af6a879e915ae7bcd83695c316ebb32e1c61bc2 (opens in a new tab)
- git.kernel.org/stable/c/8daa6c708ef524089ae43f2aed9190acb26d7df8 (opens in a new tab)
- git.kernel.org/stable/c/2fa49cc884f6496a915c35621ba4da35649bf159 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)