CVE-2025-38478comedi: Fix initialization of data for instructions that write to subdevice
Updated under an hour ago ()
Does this affect you?
It affects Linux and 2 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: comedi: Fix initialization of data for instructions that write to subdevice Some Comedi subdevice instruction handlers are known to access instruction data elements beyond the first `insn->n` elements in some cases. The `do_insn_ioctl()` and `do_insnlist_ioctl()` functions allocate at least `MIN_SAMPLES` (16) data elements to deal with this, but they do not initialize all of that. For Comedi instruction codes that write to the subdevice, the first `insn->n` data elements are copied from user-space, but the remaining elements are left uninitialized. That could be a problem if the subdevice instruction handler reads the uninitialized data. Ensure that the first `MIN_SAMPLES` elements are initialized before calling these instruction handlers, filling the uncopied elements with 0. For `do_insnlist_ioctl()`, the same data buffer elements are used for handling a list of instructions, so ensure the first `MIN_SAMPLES` elements are initialized for each instruction that writes to the subdevice.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from ed9eccbe8970f6eedc1b978c157caf1251a896d4 before 6f38c6380c3b38a05032b8881e41137385a6ce02; from ed9eccbe8970f6eedc1b978c157caf1251a896d4 before 13e4d9038a1e869445a996a3f604a84ef52fe8f4; from ed9eccbe8970f6eedc1b978c157caf1251a896d4 before 020eed5681d0f9bced73970368078a92d6cfaa9c; from ed9eccbe8970f6eedc1b978c157caf1251a896d4 before d3436638738ace8f101af7bdee2eae1bc38e9b29; from ed9eccbe8970f6eedc1b978c157caf1251a896d4 before 673ee92bd2d31055bca98a1d96b653f5284289c4; from ed9eccbe8970f6eedc1b978c157caf1251a896d4 before c42116dc70af6664526f7aa82cf937824ab42649; from ed9eccbe8970f6eedc1b978c157caf1251a896d4 before fe8713fb4e4e82a4f91910d9a41bf0613e69a0b9; from ed9eccbe8970f6eedc1b978c157caf1251a896d4 before 46d8c744136ce2454aa4c35c138cc06817f92b8e | CNA record |
linux linux_kernel linux:linux_kernel | from 2.6.29 before 5.4.297; from 5.5 before 5.10.241; from 5.11 before 5.15.190; from 5.16 before 6.1.147; from 6.2 before 6.6.100; from 6.7 before 6.12.40; from 6.13 before 6.15.8; 6.16; and 5 more ranges | NVD |
debian debian_linux debian:debian_linux | 11.0 | NVD |
References
- https://git.kernel.org/stable/c/6f38c6380c3b38a05032b8881e41137385a6ce02patch
- https://git.kernel.org/stable/c/13e4d9038a1e869445a996a3f604a84ef52fe8f4patch
- https://git.kernel.org/stable/c/020eed5681d0f9bced73970368078a92d6cfaa9cpatch
- https://git.kernel.org/stable/c/d3436638738ace8f101af7bdee2eae1bc38e9b29patch
- https://git.kernel.org/stable/c/673ee92bd2d31055bca98a1d96b653f5284289c4patch
- https://git.kernel.org/stable/c/c42116dc70af6664526f7aa82cf937824ab42649patch
- https://git.kernel.org/stable/c/fe8713fb4e4e82a4f91910d9a41bf0613e69a0b9patch
- https://git.kernel.org/stable/c/46d8c744136ce2454aa4c35c138cc06817f92b8epatch
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlmailing-list, third-party-advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlmailing-list, third-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.