CVE-2026-99063 json
dm ioctl: don't let data_start run past the buffer
published 19d ago modified 12d ago also EUVD-2026-108729
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
dm ioctl: don't let data_start run past the buffer
struct dm_ioctl has seven bytes of trailing padding, so the smallest buffer userspace is allowed to ask for, offsetof(struct dm_ioctl, data), is seven bytes shorter than sizeof(struct dm_ioctl).
get_result_buffer() sets data_start to sizeof(struct dm_ioctl) without looking at how big the buffer actually is. Ask for the minimum and data_start ends up seven bytes past the end. Callers add it to data_size, and ctl_ioctl() copies that much back to userspace:
BUG: KASAN: slab-out-of-bounds in _copy_to_user+0xad/0xd0 Read of size 312 at addr ffff8880169e4c00 by task repro-dm/140 ctl_ioctl+0x5e3/0xcb0 dm_ctl_ioctl+0x25/0x40 allocated 305-byte region [ffff8880169e4c00, ffff8880169e4d31)
A DM_LIST_DEVICES with data_size set to 305 is enough to hit it, and the seven bytes that leak are whatever sat next to the allocation.
Clamp data_start to the buffer size.
Note that this is not a security bug because the out-of-bounds read can only be triggered by root.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-99063
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99063
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-110954
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/aaa93e41ae308ad9ff9d9ba3296a0d0f4d45bad3 commit
- git.kernel.org/stable/c/f171054f3c4cfc4dc0cb622ec5b15793e5f23029 commit
- git.kernel.org/stable/c/afe80ec31464f4c54cc1bc658753bc14cb14bd6c commit
- git.kernel.org/stable/c/98195e822343a656b92e235847ab3e72b1a3f920 commit
- git.kernel.org/stable/c/e5c3f3d8935ecc64c962fb66e6a86dbf79218f61 commit
- git.kernel.org/stable/c/5680b6fb3054677d4ee65d3baba24b649f1b430e commit
- git.kernel.org/stable/c/725b49c689bbb29ef740b0d6b5ea9390baa9a695 commit
- git.kernel.org/stable/c/9b3fcf519d370df94a56f3b272d9eddffffa5be8 commit
Is CVE-2026-99063 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99063 updated cvss 2.3
kernel: dm ioctl: don't let data_start run past the buffer
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/aaa93e41ae308ad9ff9d9ba3296a0d0f4d45bad3
- git.kernel.org /stable/c/f171054f3c4cfc4dc0cb622ec5b15793e5f23029
- git.kernel.org /stable/c/afe80ec31464f4c54cc1bc658753bc14cb14bd6c
- git.kernel.org /stable/c/98195e822343a656b92e235847ab3e72b1a3f920
- git.kernel.org /stable/c/e5c3f3d8935ecc64c962fb66e6a86dbf79218f61
- git.kernel.org /stable/c/5680b6fb3054677d4ee65d3baba24b649f1b430e
- git.kernel.org /stable/c/725b49c689bbb29ef740b0d6b5ea9390baa9a695
- git.kernel.org /stable/c/9b3fcf519d370df94a56f3b272d9eddffffa5be8
Sources
- CVE List CVE-2026-99063
- NVD CVE-2026-99063
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.