CVE-2025-39686

published 5 Sep 2025 · updated 12 May 2026

comedi: Make insn_rw_emulate_bits() do insn->n samples

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7afba9221f70d4cbce0f417c558879cba0eb5e66, Kernel 842f307a1d115b24f2bcb2415c4e344f11f55930, Kernel 92352ed2f9ac422181e381c2430c2d0dfb46faa0 and 3 more.

In the Linux kernel, the following vulnerability has been resolved: comedi: Make insn_rw_emulate_bits() do insn->n samples The `insn_rw_emulate_bits()` function is used as a default handler for `INSN_READ` instructions for subdevices that have a handler for `INSN_BITS` but not for `INSN_READ`. Similarly, it is used as a default handler for `INSN_WRITE` instructions for subdevices that have a handler for `INSN_BITS` but not for `INSN_WRITE`. It works by emulating the `INSN_READ` or `INSN_WRITE` instruction handling with a constructed `INSN_BITS` instruction. However, `INSN_READ` and `INSN_WRITE` instructions are supposed to be able read or write multiple samples, indicated by the `insn->n` value, but `insn_rw_emulate_bits()` currently only handles a single sample. For `INSN_READ`, the comedi core will copy `insn->n` samples back to user-space. (That triggered KASAN kernel-infoleak errors when `insn->n` was greater than 1, but that is being fixed more generally elsewhere in the comedi core.) Make `insn_rw_emulate_bits()` either handle `insn->n` samples, or return an error, to conform to the general expectation for `INSN_READ` and `INSN_WRITE` handlers.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.29, >=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <7afba9221f70d4cbce0f417c558879cba0eb5e66, >=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <842f307a1d115b24f2bcb2415c4e344f11f55930, >=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <92352ed2f9ac422181e381c2430c2d0dfb46faa0, >=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <ab77e85bd3bc006ef40738f26f446a660813da44, >=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <ae8bc1f07bcb31b8636420e03d1f9c3df6219a2b, >=ed9eccbe8970f6eedc1b978c157caf1251a896d4 <dc0a2f142d655700db43de90cb6abf141b73d9087afba9221f70d4cbce0f417c558879cba0eb5e66, 842f307a1d115b24f2bcb2415c4e344f11f55930, 92352ed2f9ac422181e381c2430c2d0dfb46faa0, ab77e85bd3bc006ef40738f26f446a660813da44, ae8bc1f07bcb31b8636420e03d1f9c3df6219a2b, dc0a2f142d655700db43de90cb6abf141b73d908

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-39686 severity on Zeptric[![CVE-2025-39686](https://zeptric.io/badge/cve/CVE-2025-39686.svg)](https://zeptric.io/cve/CVE-2025-39686)