dm: fix a buffer overflow in ioctl processing
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in c8c5311237448f6ffeecc9aec2362e3692623668; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 448ee8fb79c26a26599ffa4b2adeb4322d3d3d8c; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 526ff9126a0ae087b65726e1faf31114c718020d; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in d271631023cbe1cbe7c31a0275ab797883be6e0a; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5af6a879e915ae7bcd83695c316ebb32e1c61bc2; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 8daa6c708ef524089ae43f2aed9190acb26d7df8; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 2fa49cc884f6496a915c35621ba4da35649bf159
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.88; From 6.13.0 · fixed in 6.18.30; From 6.19.0 · fixed in 7.0.7
References 8
git.kernel.org
- stable/c/c8c5311237448f6ffeecc9aec2362e3692623668
- stable/c/448ee8fb79c26a26599ffa4b2adeb4322d3d3d8c
- stable/c/526ff9126a0ae087b65726e1faf31114c718020d
- stable/c/f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a
- stable/c/d271631023cbe1cbe7c31a0275ab797883be6e0a
- stable/c/5af6a879e915ae7bcd83695c316ebb32e1c61bc2
- stable/c/8daa6c708ef524089ae43f2aed9190acb26d7df8
- stable/c/2fa49cc884f6496a915c35621ba4da35649bf159