Skip to main content
VulnerabilityPublished Updated

CVE-2026-46023: Linux kernel · dm mirror: fix integer overflow in create_dirty_log()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e5e0ae3237584ebef510366c4cb3d5cc7c22b610 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

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 e5e0ae3237584ebef510366c4cb3d5cc7c22b610, ae59b3025609d5a0a39cf5b2b94e2467f6231573, 249c831183fb806c8e3b14c7c4c1d2fb68cf37fb +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < e5e0ae3237584ebef510366c4cb3d5cc7c22b610
Fixed in
  • e5e0ae3237584ebef510366c4cb3d5cc7c22b610
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < ae59b3025609d5a0a39cf5b2b94e2467f6231573
Fixed in
  • ae59b3025609d5a0a39cf5b2b94e2467f6231573
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 249c831183fb806c8e3b14c7c4c1d2fb68cf37fb
Fixed in
  • 249c831183fb806c8e3b14c7c4c1d2fb68cf37fb
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 87c99a50e0fdc68a5b9b52a94d49452cd3ff02ca
Fixed in
  • 87c99a50e0fdc68a5b9b52a94d49452cd3ff02ca
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 47dad9eea75d33212d3d2cea10e7ed6a1bfc0713
Fixed in
  • 47dad9eea75d33212d3d2cea10e7ed6a1bfc0713
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 35f6b3281efd44d19110574663bc17a610bc73b9
Fixed in
  • 35f6b3281efd44d19110574663bc17a610bc73b9

Description

In the Linux kernel, the following vulnerability has been resolved: dm mirror: fix integer overflow in create_dirty_log() The argument count calculation in create_dirty_log() performs `*args_used = 2 + param_count` before validating against argc. When a user provides a param_count close to UINT_MAX via the device mapper table string, this unsigned addition wraps around to a small value, causing the subsequent `argc < *args_used` check to be bypassed. The overflowed param_count is then passed as argc to dm_dirty_log_create(), where it can cause out-of-bounds reads on the argv array. Fix by comparing param_count against argc - 2 before performing the addition, following the same pattern used by parse_features() in the same file. Since argc >= 2 is already guaranteed, the subtraction is safe.

References

Community reviews

Loading reviews…