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-37812usb: cdns3: Fix deadlock when using NCM gadget

Description

In the Linux kernel, the following vulnerability has been resolved: usb: cdns3: Fix deadlock when using NCM gadget The cdns3 driver has the same NCM deadlock as fixed in cdnsp by commit 58f2fcb3a845 ("usb: cdnsp: Fix deadlock issue during using NCM gadget"). Under PREEMPT_RT the deadlock can be readily triggered by heavy network traffic, for example using "iperf --bidir" over NCM ethernet link. The deadlock occurs because the threaded interrupt handler gets preempted by a softirq, but both are protected by the same spinlock. Prevent deadlock by disabling softirq during threaded irq handler.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 12 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-37812, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.16% · top 95% of all CVEs (16 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 7733f6c32e36ff9d7adadf40001039bf219b1cbe – < eebfb64c624fc738b669100173344fb441c5e719
    • affected 7733f6c32e36ff9d7adadf40001039bf219b1cbe – < 59a760e4796a3cd88d8b9d7706e0a638de677751
    • affected 7733f6c32e36ff9d7adadf40001039bf219b1cbe – < b96239582531775f2fdcb14de29bdb6870fd4c8c
    • affected 7733f6c32e36ff9d7adadf40001039bf219b1cbe – < c27db84ed44e50ff90d9e3a2a25fae2e0a0fa015
    • affected 7733f6c32e36ff9d7adadf40001039bf219b1cbe – < 48a62deb857f0694f611949015e70ad194d97159
    • affected 7733f6c32e36ff9d7adadf40001039bf219b1cbe – < 74cd6e408a4c010e404832f0e4609d29bf1d0c41
    • affected 7733f6c32e36ff9d7adadf40001039bf219b1cbe – < 09e90a9689a4aac7a2f726dc2aa472b0b37937b7
    • affected 7733f6c32e36ff9d7adadf40001039bf219b1cbe – < a1059896f2bfdcebcdc7153c3be2307ea319501f
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.4.293 – ≤ 5.4.*
    • unaffected 5.10.237 – ≤ 5.10.*
    • unaffected 5.15.181 – ≤ 5.15.*
    • unaffected 6.1.136 – ≤ 6.1.*
    • unaffected 6.6.89 – ≤ 6.6.*
    • unaffected 6.12.26 – ≤ 6.12.*
    • unaffected 6.14.5 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .