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-40106comedi: fix divide-by-zero in comedi_buf_munge()

Description

In the Linux kernel, the following vulnerability has been resolved: comedi: fix divide-by-zero in comedi_buf_munge() The comedi_buf_munge() function performs a modulo operation `async->munge_chan %= async->cmd.chanlist_len` without first checking if chanlist_len is zero. If a user program submits a command with chanlist_len set to zero, this causes a divide-by-zero error when the device processes data in the interrupt handler path. Add a check for zero chanlist_len at the beginning of the function, similar to the existing checks for !map and CMDF_RAWDATA flag. When chanlist_len is zero, update munge_count and return early, indicating the data was handled without munging. This prevents potential kernel panics from malformed user commands.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 6 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < 4ffea48c69cb2b96a281cb7e5e42d706996631db
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < 8f3e4cd9be4b47246ea73ce5e3e0fa2f57f0d10c
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < 2670932f2465793fea1ef073e40883e8390fa4d9
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < 6db19822512396be1a3e1e20c16c97270285ba1a
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < d4854eff25efb06d0d84c13e7129bbdba4125f8c
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < a4bb5d1bc2f238461bcbe5303eb500466690bb2c
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < 55520f65fd447e04099a2c44185453c18ea73b7e
    • affected ed9eccbe8970f6eedc1b978c157caf1251a896d4 – < 87b318ba81dda2ee7b603f4f6c55e78ec3e95974
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.4.301 – ≤ 5.4.*
    • unaffected 5.10.246 – ≤ 5.10.*
    • unaffected 5.15.196 – ≤ 5.15.*
    • unaffected 6.1.158 – ≤ 6.1.*
    • unaffected 6.6.115 – ≤ 6.6.*
    • unaffected 6.12.56 – ≤ 6.12.*
    • unaffected 6.17.6 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .