CVE-2026-99063 — dm ioctl: don't let data_start run past the buffer
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 76c072b48e39e9291fbf02d6c912cf27d65e093d and < 98195e822343a656b92e235847ab3e72b1a3f920≥ 76c072b48e39e9291fbf02d6c912cf27d65e093d and < e5c3f3d8935ecc64c962fb66e6a86dbf79218f61≥ 76c072b48e39e9291fbf02d6c912cf27d65e093d and < 5680b6fb3054677d4ee65d3baba24b649f1b430e≥ 76c072b48e39e9291fbf02d6c912cf27d65e093d and < 725b49c689bbb29ef740b0d6b5ea9390baa9a695≥ 76c072b48e39e9291fbf02d6c912cf27d65e093d and < 9b3fcf519d370df94a56f3b272d9eddffffa5be8version 2.6.25≥ 76c072b48e39e9291fbf02d6c912cf27d65e093d and < aaa93e41ae308ad9ff9d9ba3296a0d0f4d45bad3≥ 76c072b48e39e9291fbf02d6c912cf27d65e093d and < f171054f3c4cfc4dc0cb622ec5b15793e5f23029 and 1 more≥ 76c072b48e39e9291fbf02d6c912cf27d65e093d and < afe80ec31464f4c54cc1bc658753bc14cb14bd6c |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 23, 2026 – Oct 30, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
10 on the record
- git.kernel.org/stable/c/5680b6fb3054677d4ee65d3baba24b649f1b430e
- git.kernel.org/stable/c/afe80ec31464f4c54cc1bc658753bc14cb14bd6c
- nvd.nist.gov/vuln/detail/CVE-2026-99063
- git.kernel.org/stable/c/f171054f3c4cfc4dc0cb622ec5b15793e5f23029
- git.kernel.org/stable/c/98195e822343a656b92e235847ab3e72b1a3f920
- git.kernel.org/stable/c/9b3fcf519d370df94a56f3b272d9eddffffa5be8
- github.com/advisories/GHSA-vqpj-f54g-hrc3
- git.kernel.org/stable/c/e5c3f3d8935ecc64c962fb66e6a86dbf79218f61
- git.kernel.org/stable/c/725b49c689bbb29ef740b0d6b5ea9390baa9a695
- git.kernel.org/stable/c/aaa93e41ae308ad9ff9d9ba3296a0d0f4d45bad3
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-99063 is "dm ioctl: don't let data_start run past the buffer", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.