CVE-2026-72106: Linux kernel · dm-ioctl: fix a possible overflow in list_version_get_info
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e0f5842c4e2a7dbefb52a2dc6711789bc6963e55 : patch Linux kernel soon.
Data as of 30 Oct 2026, 13:33 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e0f5842c4e2a7dbefb52a2dc6711789bc6963e55, df50c24c6447c18886ed126d3d81cc7e155ea8b6, d61c12573ed9768690fdcb2bc38846a1bcb01358 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 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 30 Oct 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
|
AI-suggested
A fix is available and has been applied in multiple Linux kernel commits. Users and administrators should update affected Linux kernel versions to the fixed releases identified by the commits (e.g., e0f5842c4e2a7dbefb52a2dc6711789bc6963e55 and others). No additional mitigation is required beyond applying the official patch.
Description
A buffer overflow vulnerability was identified and fixed in the Linux kernel's dm-ioctl component, specifically in the list_version_get_info function. The issue was caused by writing 16 bytes into a buffer sized for 12 bytes, leading to potential overflow. The fix involved correcting the size used for the copy operation to match the actual structure size, preventing overflow.
References
- git.kernel.org/stable/c/3cba74d3fb2c1890ffae019301227d1366f74907 (opens in a new tab)
- git.kernel.org/stable/c/29536a9ff146d9bbd618959857ed2e691cda1d21 (opens in a new tab)
- git.kernel.org/stable/c/e0f5842c4e2a7dbefb52a2dc6711789bc6963e55 (opens in a new tab)
- git.kernel.org/stable/c/d61c12573ed9768690fdcb2bc38846a1bcb01358 (opens in a new tab)
- git.kernel.org/stable/c/df50c24c6447c18886ed126d3d81cc7e155ea8b6 (opens in a new tab)
- git.kernel.org/stable/c/76c6f845dc0c614304a6e6ee619b552f97cf24b3 (opens in a new tab)