Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39684comedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl()

Description

In the Linux kernel, the following vulnerability has been resolved: comedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl() syzbot reports a KMSAN kernel-infoleak in `do_insn_ioctl()`. A kernel buffer is allocated to hold `insn->n` samples (each of which is an `unsigned int`). For some instruction types, `insn->n` samples are copied back to user-space, unless an error code is being returned. The problem is that not all the instruction handlers that need to return data to userspace fill in the whole `insn->n` samples, so that there is an information leak. There is a similar syzbot report for `do_insnlist_ioctl()`, although it does not have a reproducer for it at the time of writing. One culprit is `insn_rw_emulate_bits()` which is used as the handler for `INSN_READ` or `INSN_WRITE` instructions for subdevices that do not have a specific handler for that instruction, but do have an `INSN_BITS` handler. For `INSN_READ` it only fills in at most 1 sample, so if `insn->n` is greater than 1, the remaining `insn->n - 1` samples copied to userspace will be uninitialized kernel data. Another culprit is `vm80xx_ai_insn_read()` in the "vm80xx" driver. It never returns an error, even if it fails to fill the buffer. Fix it in `do_insn_ioctl()` and `do_insnlist_ioctl()` by making sure that uninitialized parts of the allocated buffer are zeroed before handling each instruction. Thanks to Arnaud Lecomte for their fix to `do_insn_ioctl()`. That fix replaced the call to `kmalloc_array()` with `kcalloc()`, but it is not always necessary to clear the whole buffer.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39684, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 92% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < 868a1b68dcd9f2805bb86aa64862402f785d8c4a
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < ff4a7c18799c7fe999fa56c5cf276e13866b8c1a
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < d84f6e77ebe3359394df32ecd97e0d76a25283dc
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < f3b0c9ec54736f3b8118f93a473d22e11ee65743
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < aecf0d557ddd95ce68193a5ee1dc4c87415ff08a
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < 3cd212e895ca2d58963fdc6422502b10dd3966bb
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.44 – ≤ 6.12.*
    • unaffected 6.16.4 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39684 badge
[![CVE-2025-39684](https://cveledger.app/badge/CVE-2025-39684.svg)](https://cveledger.app/cve/CVE-2025-39684)

Record last updated .