Review reviewHigh

CVE-2026-46294

Linux Linux, linux kernel

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...

CVSS
7.8
EPSS
0.14%
4.03% percentile
CISA KEV
Not listed
Published
2026.06.09
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c8c5311237448f6ffeecc9aec2362e3692623668, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 448ee8fb79c26a26599ffa4b2adeb4322d3d3d8c, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 526ff9126a0ae087b65726e1faf31114c718020d, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d271631023cbe1cbe7c31a0275ab797883be6e0a, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5af6a879e915ae7bcd83695c316ebb32e1c61bc2, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 8daa6c708ef524089ae43f2aed9190acb26d7df8, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2fa49cc884f6496a915c35621ba4da35649bf159, >= 2.6.12, >= 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
Fixed versions
5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787