comedi: Fix initialization of data for instructions that write to subdevice
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.297, 5.10.241, 5.15.190, 6.1.147, 6.6.100, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From ed9eccbe8970f6eedc1b978c157caf1251a896d4 · fixed in 6f38c6380c3b38a05032b8881e41137385a6ce02; From ed9eccbe8970f6eedc1b978c157caf1251a896d4 · fixed in 13e4d9038a1e869445a996a3f604a84ef52fe8f4; From ed9eccbe8970f6eedc1b978c157caf1251a896d4 · fixed in 020eed5681d0f9bced73970368078a92d6cfaa9c; From ed9eccbe8970f6eedc1b978c157caf1251a896d4 · fixed in d3436638738ace8f101af7bdee2eae1bc38e9b29; From ed9eccbe8970f6eedc1b978c157caf1251a896d4 · fixed in 673ee92bd2d31055bca98a1d96b653f5284289c4; From ed9eccbe8970f6eedc1b978c157caf1251a896d4 · fixed in c42116dc70af6664526f7aa82cf937824ab42649; From ed9eccbe8970f6eedc1b978c157caf1251a896d4 · fixed in fe8713fb4e4e82a4f91910d9a41bf0613e69a0b9; From ed9eccbe8970f6eedc1b978c157caf1251a896d4 · fixed in 46d8c744136ce2454aa4c35c138cc06817f92b8e
- Linux Linux
2.6.29
- KernelLinux
From 2.6.29 · fixed in 5.4.297; From 5.5.0 · fixed in 5.10.241; From 5.11.0 · fixed in 5.15.190; From 5.16.0 · fixed in 6.1.147; From 6.2.0 · fixed in 6.6.100; From 6.7.0 · fixed in 6.12.40; From 6.13.0 · fixed in 6.15.8
References 8
git.kernel.org
- stable/c/6f38c6380c3b38a05032b8881e41137385a6ce02
- stable/c/13e4d9038a1e869445a996a3f604a84ef52fe8f4
- stable/c/020eed5681d0f9bced73970368078a92d6cfaa9c
- stable/c/d3436638738ace8f101af7bdee2eae1bc38e9b29
- stable/c/673ee92bd2d31055bca98a1d96b653f5284289c4
- stable/c/c42116dc70af6664526f7aa82cf937824ab42649
- stable/c/fe8713fb4e4e82a4f91910d9a41bf0613e69a0b9
- stable/c/46d8c744136ce2454aa4c35c138cc06817f92b8e